Adds cluster API example requests and responses

[szabosteve]

Overview

Related to #2482.
This PR adds request and response examples to the cluster APIs.

[github-actions]

Following you can find the validation results for the APIs you have changed.

API	Status	Request	Response
cluster.allocation_explain	🔴	5/5	1/5
cluster.health	🟢	153/153	153/153
cluster.put_settings	🟢	58/58	57/57
cluster.reroute	🟢	6/6	5/5
nodes.info	🔴	116/116	1/116
nodes.reload_secure_settings	🟢	2/2	2/2
tasks.get	🟢	10/10	10/10

You can validate these APIs yourself by using the make validate target.

[lcawl]

LGTM. Let me know if you want me to add the updates to the overlay files in this same PR

[github-actions]

Following you can find the validation results for the APIs you have changed.

API	Status	Request	Response
cluster.allocation_explain	🟢	4/4	4/4
cluster.health	🟢	153/153	153/153
cluster.put_settings	🟢	58/58	57/57
cluster.reroute	🟢	6/6	5/5
nodes.info	🔴	113/113	1/113
nodes.reload_secure_settings	🟢	2/2	2/2
tasks.get	🟢	10/10	10/10

You can validate these APIs yourself by using the make validate target.

[github-actions]

Following you can find the validation results for the APIs you have changed.

API	Status	Request	Response
cluster.allocation_explain	🟢	4/4	4/4
cluster.health	🟢	153/153	153/153
cluster.put_settings	🟢	58/58	57/57
cluster.reroute	🟢	6/6	5/5
nodes.info	🔴	113/113	1/113
nodes.reload_secure_settings	🟢	2/2	2/2
tasks.get	🟢	10/10	10/10

You can validate these APIs yourself by using the make validate target.

[github-actions]

Following you can find the validation results for the APIs you have changed.

API	Status	Request	Response
cluster.allocation_explain	🟢	4/4	4/4
cluster.health	🟢	153/153	153/153
cluster.put_settings	🟢	58/58	57/57
cluster.reroute	🟢	6/6	5/5
nodes.info	🔴	113/113	1/113
nodes.reload_secure_settings	🟢	2/2	2/2
tasks.get	🟢	10/10	10/10

You can validate these APIs yourself by using the make validate target.

[github-actions]

Following you can find the validation results for the APIs you have changed.

API	Status	Request	Response
cluster.allocation_explain	🟢	4/4	4/4
cluster.health	🟢	153/153	153/153
cluster.put_settings	🟢	58/58	57/57
cluster.reroute	🟢	6/6	5/5
nodes.info	🔴	113/113	1/113
nodes.reload_secure_settings	🟢	2/2	2/2
tasks.get	🟢	10/10	10/10

You can validate these APIs yourself by using the make validate target.

[github-actions]

Following you can find the validation results for the APIs you have changed.

API	Status	Request	Response
cluster.allocation_explain	🟢	4/4	4/4
cluster.health	🟢	153/153	153/153
cluster.put_settings	🟢	58/58	57/57
cluster.reroute	🟢	6/6	5/5
nodes.info	🔴	113/113	1/113
nodes.reload_secure_settings	🟢	2/2	2/2
tasks.get	🟢	10/10	10/10

You can validate these APIs yourself by using the make validate target.

[lcawl]

I added a *.yaml file to this PR for your consideration. Right now all the *.json examples are returning linting errors like this:

 105666:17      warning  oas3-schema                 Property "type" is not expected to be here.                                         components.examples.nodesInfoResponseExample1.type
 105667:26      warning  oas3-schema                 Property "response_code" is not expected to be here.                                components.examples.nodesInfoResponseExample1.response_code

I tried converting the example to a YAML file then commenting out the extra fields (since yaml allows comments whereas json doesn't). This succeeds in solving the linting errors (since the comment fields are not carried forward to the output). Is this acceptable to use YAML instead of JSON format and is it okay to comment out those extra fields?