Full End to End OAS Automation for Rule creation Endpoint

[XavierM]

At first, we need to validate that this POC can be used to generate OpenAPI Specification (OAS) documentation for our rule creation REST APIs.
Secondly, we will have to finish the conversion of our APIs to the http versioning. Therefore, we do not create a bigger mess with our routes types.
Then, we will have to create a buildkite scripts into kibana to update our OAS documentation automatically when one of our route type changed.
Finally, we will update our types to all of our routes to have a full End to End OAS for rules endpoints.

[elasticmachine]

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

[JiaweiWu]

POC to verify rule params being generated by OAS: #179212

Moving this to on hold for now, since we need to wait for core to merge the router changes first.

[cnasikas]

Closing in favor of #157883 and #187574