Write test(s) to ensure that all TypeConverter and Editor Attributes on internals are properly routed

[zsd4yr]

For each TypeConverter and Editor attribute connecting a type to its type converter or editor by a fully qualified string, we need a TypeForwardTo attribute in the corresponding facade. This is required as GenFacades will not automatically generate TypeForwardTo statements for internals.

Please see #2078 (comment) for more details on the history of this need and discussion.

Suggestion: write a unit test that rolls over every assembly we own and uses reflection to determine which internal types, properties, and methods have these attributes. Then, for each of those that exist, determine whether or not that type was in an assembly that we now type forward from. If so, ensure that there is a manually added TypeForwardTo statement in the facades.

[weltkante]

use reflection to determine which internal types, properties, and methods have these attributes

That statement is misleading, you want to figure out all internal types which are targeted by TypeConverter/Editor attributes within WinForms:

• methods shouldn't have TypeConverter/Editor attributes
• you scan all types/props, not just internal ones
• you look for attributes referencing internal types in their argument