Partitioning: Design and implement partitioning strategy for Audit Events
Updating the description to indicate the remaining work. The following issues are required for us to consider audit_events as successfully deployed Blocking Issue - [Partitioning: UI/UX Changes needed to encourage optimal querying of partitioned audit_events](https://gitlab.com/gitlab-org/gitlab/-/issues/223260) Required Issues - [Swap base audit_events table with partitioned copy](https://gitlab.com/gitlab-org/gitlab/-/issues/241267) - [Cleanup background migration for partitioning audit_events](https://gitlab.com/gitlab-org/gitlab/-/issues/229903) - [Expose metric to observe state of dynamic partitioning](https://gitlab.com/gitlab-org/gitlab/-/issues/227353) Nice to have (but not required) - [Document design decisions for partitioning audit events](https://gitlab.com/gitlab-org/gitlab/-/issues/217489) - [Determine if partitioning audit_events improved performance and scale](https://gitlab.com/gitlab-org/gitlab/-/issues/238223) - [Partitioning: Enforce partitioning key in queries, detect queries without it](https://gitlab.com/gitlab-org/gitlab/-/issues/216654) - [Refactor audit_events to use jsonb](https://gitlab.com/gitlab-org/gitlab/-/issues/216930)
epic