Private/Custom UI components

[schottra]

It might be useful for the UI to support private/custom UI components that are installed/loaded at runtime. There are a couple of use cases:

• Flyte users can write custom tasks that produce custom output. To the UI, this output is just an object with no semantic meaning to the fields. But a custom UI plugin might be able to render that output in a more useful way
• Some users/companies may have a desire to show related/linked metrics for an Execution as additional tabs in the ExecutionDetails view (next to the Nodes/Graph tabs). Those custom views might reach out to internal, private systems for their data.

From the standpoint of Flyte Console, we merely need to know that these plugins exist and give them space/data to do their work. My initial thought is that it makes sense to define a React Component interface for each case where we allow extensions/overrides, document those, and maybe create a sandbox to let people play around in for testing.
"Installation" of the component could be including a script/bundle that calls a global function to install the hooks. This needs a little more definition.

[EngHabu]

Bug bankruptcy

[anrusina]

FlyteDeck should solve it, not needed due to https://github.com/flyteorg/flyteconsole/issues/469