[SPIKE] Use Helix instancing to save memory for large number of mesh geometry

[aparajit-pratap]

Purpose

Trial implementation exploring using Helix instancing to render large number of mesh geometry.
This goes hand-in-hand with corresponding LibG changes here: https://git.autodesk.com/Dynamo/LibG/pull/1080

Assumptions

• This assumes that any node producing mesh geometry (solids and surfaces) and participating in replication can potentially benefit from instancing while being rendered.

Issues

• Instances do not currently display in the background preview for some reason
• Geometry transforms are incorrect in LibG (e.g. if a Sphere is located away from the origin, it's transform matrix does not reflect its exact position)

Declarations

Check these if you believe they are true

• The codebase is in a better state after this PR
• Is documented according to the standards
• The level of testing this PR includes is appropriate
• User facing strings, if any, are extracted into *.resx files
• All tests pass using the self-service CI.
• Snapshot of UI changes, if any.
• Changes to the API follow Semantic Versioning and are documented in the API Changes document.
• This PR modifies some build requirements and the readme is updated

[mjkkirschner]

hmm - we should inspect the EffectsManager at runtime to see if theres an effect for instancing meshes - it may try to use our shader.

[mjkkirschner]

does this somehow conflict with line this line below:
id = ((rp.RequiresCustomTransform) ? rp.Description : baseId) + PointsKey;

[mjkkirschner]

@aparajit-pratap I think in our vertex shaders we'll need to add something like this:

https://github.com/DynamoDS/Dynamo/blob/RC2.5.0_master/src/DynamoCoreWpf/ViewModels/Watch3D/Shaders/Custom.fx#L157

coming back this after thinking about it for another few minutes:
I think this is more likely to work:
https://github.com/helix-toolkit/helix-toolkit/blob/develop/Source/HelixToolkit.Native.ShaderBuilder/VS/vsMeshDefault.hlsl#L37

[mjkkirschner]

Another thought on this type of approach - opposed to just replicated calls, it would also be good to try this on calls like move or scale, rotate etc- where instancing and transforming is exactly what the node does and instancing will definitely work.