Fixes for API specification

[delvedor]

After #42346, some documentation link the and definition of slm.delete_lifecycle were not correct, this pr fixes them.

Related: #44487 #45102
This should also be backported to 7.x.

cc @elastic/es-clients

[elasticmachine]

Pinging @elastic/es-distributed

[dakrone]

I left a comment, this ends up adding an invalid endpoint

[dakrone]

SLM delete policy does not support a path without the {policy_id} parameter, it's not allowed at all

[delvedor]

Thanks @dakrone! I was under the impression that a path without the policy_id was allowed, because in the original implementation, before the new spec format, the policy_id was not marked as required: https://github.com/elastic/elasticsearch/blob/a2e0db7783055300de77f3a0e525a21ac2bd7530/x-pack/plugin/src/test/resources/rest-api-spec/api/slm.delete_lifecycle.json

I'll update the spec.

[elasticmachine]

Pinging @elastic/es-core-features

[elasticmachine]

Pinging @elastic/es-core-infra

[polyfractal]

Had a look at error_trace failures. Those are being caused by this change:

-  "description": "Parameters that are accepted by all API endpoints.",
-  "documentation": "https://www.elastic.co/guide/en/elasticsearch/reference/current/common-options.html",
+  "documentation": {
+    "url": "https://www.elastic.co/guide/en/elasticsearch/reference/current/common-options.html",
+    "description": "Parameters that are accepted by all API endpoints."
+  },

It looks like the parsing for _common.json assumes there is only one object to parse. With this change there are now two objects, and I believe it's exiting the parsing early so some of the default options are not being applied correctly... which means error_trace is being used on APIs that don't support it.

Gonna tag :core/infra on this since the parser probably needs a tweak to conform to the new schema in #42346