Remove the need for visualization files from analytics dashboards

Problem to solve

At this moment in time, visualizations are stored separately from the dashboards as individual YAML files. The visualizations are then added to the dashboards through the YAML filename.

This approach is heavy-handed for our customer use-cases, and can lead to:

1. Multiples of the same visualization file being created because the customer isn't aware that the visualization already exists.
2. Visualization file overload — overcomplicating the selection process for customers.
3. Complexities with copy/create from chart functionality as we have to save the visualization file, ask the user to add it to a dashboard, and then save it. Having it added directly to a dashboard would save the initial saving step.
4. Additional configuration steps makes it harder to create a more declarative custom dashboards framework.

Proposed solution

TBD