Remove dscom BuildTask And use CLI Only

[carstencodes]

As observed in #104, MsBuild does not play well with the DsCom Library hosted within the MsBuild Tool.

We kept the task to investigate the issue more further, but forgot to removed it when closing #104.

In #278 @bclothier stated corerctly, if the task is not supported, it should be removed from source code and documentation:

FYI the documentation seems to imply that both are in use, that the client tool would be only used if 32-bit target is selected. On the review, and if I understand you correctly, the client tool is currently always used and the build task is never used unless I pass false explicitly to the "private" property _DsComForceToolUsage which the documentation does explicitly say to not do.

I think the documentation should be updated to indicate that client tool is always used. > In particular this passage:

dscom/README.md

Lines 241 to 245 in 869f481

	The native build task is automatically selected, if a .NET 4.8 or .NET 6.0 assembly for Windows is being build using an x64 platform.
	#### Using the CLI based task
	The CLI task is automatically selected, if a .NET Standard 2.0 assembly is build. It is also chosen, if the target platform is set to x86.

---

Originally posted by @bclothier in #278 (comment)