[DOCS] Edits rollup summaries

[lcawl]

Relates to #3226

This PR edits the rollup APIs in https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-rollup based on the information from https://www.elastic.co/guide/en/elasticsearch/reference/master/rollup-apis.html

Preview

The extra content copied into the description of the "delete a rollup job" API looks like this in Bump.sh:

[github-actions]

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

API	Status	Request	Response
rollup.delete_job	🟢	3/3	3/3
rollup.get_jobs	🟢	10/10	10/10
rollup.put_job	🟢	22/22	22/22

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
rollup.delete_job	🟢	3/3	3/3
rollup.get_jobs	🟢	10/10	10/10
rollup.get_rollup_caps	🟢	3/3	3/3
rollup.get_rollup_index_caps	🟢	7/7	7/7
rollup.put_job	🟢	22/22	22/22
rollup.rollup_search	🟢	18/18	18/18
rollup.start_job	🟢	6/6	6/6
rollup.stop_job	🟢	5/5	5/5

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
rollup.delete_job	🟢	3/3	3/3
rollup.get_jobs	🟢	10/10	10/10
rollup.get_rollup_caps	🟢	3/3	3/3
rollup.get_rollup_index_caps	🟢	7/7	7/7
rollup.put_job	🟢	22/22	22/22
rollup.rollup_search	🟢	18/18	18/18
rollup.start_job	🟢	6/6	6/6
rollup.stop_job	🟢	5/5	5/5

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

[karenzone]

Left nitpick inline. Otherwise, LGTM

[karenzone]

Suggested change

"description": "Delete a rollup job.\n\nA job must be stopped first before it can be deleted.\nIf you attempt to delete a started job, an error occurs.\nSimilarly, if you attempt to delete a nonexistent job, an exception occurs.\n\nIMPORTANT: When you delete a job, you remove only the process that is actively monitoring and rolling up data.\nThe API does not delete any previously rolled up data.\nThis is by design; a user may wish to roll up a static data set.\nBecause the data set is static, after it has been fully rolled up there is no need to keep the indexing rollup job around (as there will be no new data).\nThus the job can be deleted, leaving behind the rolled up data for analysis.\nIf you wish to also remove the rollup data and the rollup index contains the data for only a single job, you can delete the whole rollup index.\nIf the rollup index stores data from several jobs, you must issue a delete-by-query that targets the rollup job's identifier in the rollup index. For example:\n\n```\nPOST my_rollup_index/_delete_by_query\n{\n \"query\": {\n \"term\": {\n \"_rollup.id\": \"the_rollup_job_id\"\n }\n }\n}\n```",

"description": "Delete a rollup job.\n\nA job must be stopped before it can be deleted.\nIf you attempt to delete a started job, an error occurs.\nSimilarly, if you attempt to delete a nonexistent job, an exception occurs.\n\nIMPORTANT: When you delete a job, you remove only the process that is actively monitoring and rolling up data.\nThe API does not delete any previously rolled up data.\nThis is by design; a user may wish to roll up a static data set.\nBecause the data set is static, after it has been fully rolled up there is no need to keep the indexing rollup job around (as there will be no new data).\nThus the job can be deleted, leaving behind the rolled up data for analysis.\nIf you wish to also remove the rollup data and the rollup index contains the data for only a single job, you can delete the whole rollup index.\nIf the rollup index stores data from several jobs, you must issue a delete-by-query that targets the rollup job's identifier in the rollup index. For example:\n\n```\nPOST my_rollup_index/_delete_by_query\n{\n \"query\": {\n \"term\": {\n \"_rollup.id\": \"the_rollup_job_id\"\n }\n }\n}\n```",

[github-actions]

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

API	Status	Request	Response
rollup.delete_job	🟢	3/3	3/3
rollup.get_jobs	🟢	10/10	10/10
rollup.get_rollup_caps	🟢	3/3	3/3
rollup.get_rollup_index_caps	🟢	7/7	7/7
rollup.put_job	🟢	22/22	22/22
rollup.rollup_search	🟢	18/18	18/18
rollup.start_job	🟢	6/6	6/6
rollup.stop_job	🟢	5/5	5/5

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
rollup.delete_job	🟢	3/3	3/3
rollup.get_jobs	🟢	10/10	10/10
rollup.get_rollup_caps	🟢	3/3	3/3
rollup.get_rollup_index_caps	🟢	7/7	7/7
rollup.put_job	🟢	22/22	22/22
rollup.rollup_search	🟢	18/18	18/18
rollup.start_job	🟢	6/6	6/6
rollup.stop_job	🟢	5/5	5/5

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
rollup.delete_job	🟢	3/3	3/3
rollup.get_jobs	🟢	10/10	10/10
rollup.get_rollup_caps	🟢	3/3	3/3
rollup.get_rollup_index_caps	🟢	7/7	7/7
rollup.put_job	🟢	22/22	22/22
rollup.rollup_search	🟢	18/18	18/18
rollup.start_job	🟢	6/6	6/6
rollup.stop_job	🟢	5/5	5/5

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