Spike: Dashboard Data Exploration

@lfarina8: I'd love for this spike exercise to be significantly more about big picture thinking, less "let's plug in one source of data" as we know that can design us into a corner very quickly. With the idea of "how might we" explore all different data sources at GitLab from a single user experience, where would we encounter hiccups? Would it be data model collisions, would it be that a single filter bar wouldn't have the flexibility to toggle between data sources easily? Could there be an opportunity to mix GLQL supported querying for plan data AND another filter experience for queries that aren't yet supported by GLQL?

I think maybe a good way to think about this is in the context of two dashboards:

1. As an engineering team, every day during standup, we want to look at one dashboard that tells us how we are doing in relation to our devsecops flow. We will need to see:
   1. Table with current open MRs
   2. Count of critical and high vulnerabilities introduced in the last x days
   3. Issues assigned to our current milestone (or label/status, whatever pivot the team would want to look at their current work)
   4. Recent pipeline failures or slow jobs
   5. Something around DORA metrics
2. As an internal GitLab PM, I want to track the MAU/WRU of my feature (event data that we are tracking for usage and behavior that wouldn't be customer facing)
   1. This may also include tracking specific clicks from other areas or going to other areas of the product that would demonstrate a common workflow.