feat: dynamic component routing for operation drilldown

[mwdchang]

Summary

Using <component> to instantiate the drilldown-components dynamically. This will:

• Keep the size of the template section nearly constant
• Allows for a more plug-and-play style: we can import components at runtime via await import(path_to_component) and add them into the registry
• Better enforcement of behaviours across components

Next up are the operation-nodes, they will need to go through some major refactoring, as some of them have the the core-logic embedded in the nodes and need to be shifted to the drilldowns.

Also:

• I also cleaned out the Julia stratify from the workflow.
• Cleaned out droppedAssetId hook to set the state, we can directly set the state on node-creation

Testing

No functional changes, workflow should work as before.

[blanchco]

Looks good, I will need to think if this will clash with our ideas on how we are making the generic drilldown template but it might not be an issue. This looks a lot cleaner