Consider adding metadata to embedded workflows using assembly proxy classes

[glopesdev]

The options for including metadata in embedded workflows packed with package assemblies are currently very limited. Apart from the description field, it is not possible to express any of the richness and flexibility of class attributes, e.g for indicating that an embedded workflow is obsolete, or that it should use a specific display name, etc.

One option to allow such flexibility would be to use proxy types in the assembly that would work as stand-in hosts for metadata associated with the embedded workflow. There could be a simple naming convention rule to associate these host classes with the embedded workflow. For example, assuming an embedded path MyAssembly:MyNamespace.MyFile.bonsai, the corresponding type name might be MyAssembly.MyNamespace.MyFile.

When loading package embedded workflows into the toolbox, the editor could look for the existence of the corresponding host class, and if present, use the attribute metadata associated with that type for the toolbox.

Another advantage of such an approach is that it would require no changes to core types and packages, as this strategy could be applied and used only at the editor level.