Need general diagnostic tracing added to runtime and interop assemblies

[Scottj1s]

There are a few paths that can fail at runtime and would benefit greatly with some trace logging, such as:

• Helper type not found: this can indicate an internal projection error
• Attempt to combine legacy RCWs (ComImport) with C#/WinRT
• OS factory activation failed, falling back to file-based: this can indicate a manifest issue
• Factory ActivateInstance failed: this can indicate loader/dependency issue

For ActivateInstance failures, specific messages for common errors would be helpful: ERROR_MOD_NOT_FOUND: this can indicate VCRT forwarders missing ERROR_PROC_NOT_FOUND: this indicates the target DLL is not a WinRT component ERROR_BAD_FORMAT: this indicates an arch mismatch in the component dll

How to: Use TraceSource and Filters with Trace Listeners