Draft: [POC] Create a basic dashboard layout framework use-case

What does this MR do and why?

Create a basic dashboard use-case that adheres to the guidelines in Dashboards layout framework design document (gitlab-com/content-sites/handbook!12928 - merged).

Note: This is a second attempt at Draft: [POC] Create a basic dashboard use-case (!187126 - closed).

What does this do:

• Reimplements the Security group-level dashboard as a simple hardcoded configuration driven dashboard.
• Standerdizes the Security dashboard by using GlDashboardPanel and the shared GridstackWrapper components that are also used by Analytics Dashboards.
• Adds an example panel to show possible panel behaviours

What does this not do:

• Add the ability to save any customizations users make to the dashboard, although there will be an upgrade path to do this.
• Add query driven visualizations
• Make use of the existing visualization types (LineChart, etc)

What's left to do to take this to production:

• Security dashboards chart components currently are rendered using the SecurityDashboardCard which strays from the GitLab-UI GlDashboardPanel UI/UX (title, padding). This could be fixed by either updating SecurityDashboardCard to render the GlDashboardPanel internally or changing how sec charts are rendered.
• Optional: Update project-level security dashboards to the same standard.

Next steps

Create a reusable dashboard layout component and document migration guides as part of Improve dashboard layout framework architecture... (#541406 - closed).

References

Screenshots or screen recordings

How to set up and validate locally

View the security dashboard at [GDK_HOST]/groups/gitlab-org/-/security/dashboard

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.