Stack formatting in DAG visualizer

[bcdurak]

• The stack is on the same level as the components: This is semantically wrong, and also different than what we do when visualizing the stack for a run template.
• If a component has settings, the component type (e.g. Orchestrator in this case) is shifted to the left to make place for the copy button. That copy button however is hidden by default, which means the layout looks off
• Clicking on a component tile behaves differently when having settings or not:
  • When there are settings, clicking it collapses/expands the settings
  • When there are no settings, it links to the component detail screen

[znegrin]

@tzador I was reviewing the designs, and there was a design for the stack dropdown that is also in the Run templates page, but I think it was never implemented exactly as in the designs. Maybe @Cahllagerfeld has more context.

This is how it was designed:

And this is how it looks currently in the run templates:

So I guess we need to decide if we go with the approach that was in the designs with the compact dropdowns, or if we try to do a new design that is more aligned with the current components. What do you think @tzador @Cahllagerfeld?

[Cahllagerfeld]

@znegrin How should the interaction look like for linking to the respecitve components?