Add technical note and caveats of data objects

[glopesdev]

This PR adds an extra technical note about dynamic data object type signatures and a warning about their caveats and limitations regarding serialization and custom scripting extensions.

[banchan86]

Hmm I have some trouble understanding what is going on in the first note, would it help to add an example bonsai workflow?

[bruno-f-cruz]

I think I would include a short one line Tip on what are the cases where these dynamic classes are suited for. I would include operators that leverage attribute names (Writers and Visualizers) and general code sanitization where dynamic classes are serve to increase readability of workflows.

[bruno-f-cruz]

Hmm I have some trouble understanding what is going on in the first note, would it help to add an example bonsai workflow?

New (1 as Foo, "a" as Bar) != new("a" as Bar, 1 as Foo). These would be two distinct dynamic classes.

However if the order is the same, they evaluate to the same ephemeral type.

[banchan86]

Hmm I have some trouble understanding what is going on in the first note, would it help to add an example bonsai workflow?

New (1 as Foo, "a" as Bar) != new("a" as Bar, 1 as Foo). These would be two distinct dynamic classes.

However if the order is the same, they evaluate to the same ephemeral type.

ah ok i got it now!