Implement top level MR types - Bugs, Features, Maintenance

From Engineering Analytics team discussion last week https://docs.google.com/document/d/1daqEon2jVKzd-dagxXEb1epNxn2v3soCx7n7s0tgfGk/edit#bookmark=id.3cmgt63oiqe2

Update the worktypes / issue dimensions: https://about.gitlab.com/handbook/engineering/metrics/#work-type-classification

• Types
  • Bugs
  • Features
  • Maintenance
• Community Contributions: true|false
• Security:true|false
• Documentation: true|false

Question: Is feature:addition vs feature:enhancement still interesting? If so, capture as scoped label or it’s own dimension? Tooling: true|false

@gl-quality/eng-analytics @kwiebers (feel free to include EP team when this is more flushed out)

Tasks

• Label rename to capture top level types gitlab-org/gitlab#28135 (closed) (new direction w/ updated tasks below)
• Refresh the engineering groups dashboards (new direction w/ updated tasks below)
• Implement PI at CTO/Engineering level (new direction w/ updated tasks below)
• Create new SSoT to represent at both CTO / VP-Development https://app.periscopedata.com/app/gitlab/976817/Merge-Request-Types
• Add Section and Product groups drill down for https://app.periscopedata.com/app/gitlab/976817/Merge-Request-Types
• Add filterable details dashboard to diagnose MR types in each teamLink to this from the top view & drill down dashboard https://app.periscopedata.com/app/gitlab/976854/Merge-Request-Types-Detail
• Add SQL change to filter out all bot created MRs
• Update PIs at both CTO and VP-development to use new SSoT => !97004 (merged)
• Work on type improvements Improve MR type classification #13068 (closed)
• Prep finance on removal of bot created MRs, only measure human efforts/investments
  • Keep existing artifacts for finance
  • Determine time to transition over for audit purposes, equip finance w/ back story
• Resolve few missing charts at team level

cc @edjdev for awareness