[ResponseOps][Rules] MW API enhancements

[cnasikas]

Teams like SREs are using automated tools (like Terraform) to manage their monitoring rules. The same would apply to the Maintenance window feature. To be able to use the MW in an automated way we need to make the MV APIs public. Before doing that, we should audit all of the MW APIs, remove or change any properties that we are not comfortable exposing, and enhancement them with new capabilities.

DoD

Preview Give feedback

1. [ResponseOps][MW] Maintenance window public APIs #198685
   Feature:Alerting Team:ResponseOps +2
2. [ResponseOps][Maintenance Window] Remove MW scoped query feature flag #172900
   Feature:Alerting/RulesManagement Team:ResponseOps backport:skip release_note:skip v8.16.0 +5
3. [ResponseOps][MW] Server side pagination support for the maintenance windows page #193076
   Team:ResponseOps +1
   

cc @elkargig @heespi @kobelb

[elasticmachine]

Pinging @elastic/response-ops (Team:ResponseOps)

[shanisagiv1]

And also remove the "tech preview" label once its done. @cnasikas thanks!

[heespi]

Before going GA we should also check the UI and finalize the capabilities we want to offer to our users.

@shanisagiv1... In terms of the above, could we outline explicitly any capabilities that would be missing and blocking GA?

@cnasikas .. based on @shanisagiv1´s thougths, we´d please need to add those to the DoD, which in turn might end up impacting the T-Shirt Size and requiring a break down into more issues?

[cnasikas]

Hey @heespi we are working with @shanisagiv1 on it. I will update the issue when we are done. Thanks!