Add @doc_tag to override default tag behaviour

[lcawl]

Fixes #2310

This PR adds a @doc_tag modifier so that we can override the default operation-level tags that are based on the namespace.

For example, we can use it to put a "data stream" tag on the create data stream API to match its grouping in the existing docs (https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-create-data-stream.html) rather than the default "indices" value.

[github-actions]

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

API	Status	Request	Response
indices.create_data_stream	🟢	29/29	29/29

You can validate this API yourself by using the make validate target.

[github-actions]

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

API	Status	Request	Response
indices.create_data_stream	🟢	29/29	29/29

You can validate this API yourself by using the make validate target.

[github-actions]

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

API	Status	Request	Response
indices.create_data_stream	🟢	29/29	29/29

You can validate this API 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
indices.create_data_stream	🟢	29/29	29/29
indices.data_streams_stats	🟢	4/4	4/4
indices.delete_data_stream	🟢	28/28	28/28
indices.migrate_to_data_stream	⚪	Missing test	Missing test
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_job	🔴	219/227	223/225
ml.put_trained_model	🔴	15/16	6/16
search_application.put_behavioral_analytics	🟢	3/3	3/3

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
indices.create_data_stream	🟢	29/29	29/29
indices.data_streams_stats	🟢	4/4	4/4
indices.delete_data_stream	🟢	28/28	28/28
indices.migrate_to_data_stream	⚪	Missing test	Missing test
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_job	🔴	219/227	223/225
ml.put_trained_model	🔴	15/16	6/16
search_application.put_behavioral_analytics	🟢	3/3	3/3

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
indices.create_data_stream	🟢	29/29	29/29
indices.data_streams_stats	🟢	4/4	4/4
indices.delete_data_stream	🟢	28/28	28/28
indices.migrate_to_data_stream	⚪	Missing test	Missing test
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_job	🔴	219/227	223/225
ml.put_trained_model	🔴	15/16	6/16
search_application.put_behavioral_analytics	🟢	3/3	3/3

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
indices.create_data_stream	🟢	29/29	29/29
indices.data_streams_stats	🟢	4/4	4/4
indices.delete_data_stream	🟢	28/28	28/28
indices.migrate_to_data_stream	⚪	Missing test	Missing test
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_job	🔴	219/227	223/225
ml.put_trained_model	🔴	15/16	6/16
search_application.put_behavioral_analytics	🟢	3/3	3/3

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

[github-actions]

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

API	Status	Request	Response
indices.create_data_stream	🟢	29/29	29/29

You can validate this API yourself by using the make validate target.

[github-actions]

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

API	Status	Request	Response
indices.create_data_stream	🟢	29/29	29/29

You can validate this API yourself by using the make validate target.

[Anaethelion]

LGTM
I've left a code suggestion to avoid using expect which simplifies a bit the code.

[github-actions]

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

API	Status	Request	Response
indices.create_data_stream	🟢	29/29	29/29

You can validate this API yourself by using the make validate target.

[github-actions]

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

API	Status	Request	Response
indices.create_data_stream	🟢	29/29	29/29

You can validate this API yourself by using the make validate target.

[github-actions]

The backport to 8.x failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-8.x 8.x
# Navigate to the new working tree
cd .worktrees/backport-8.x
# Create a new branch
git switch --create backport-2961-to-8.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 5f59dc31bbf456d0c1f5f3020ce36091b7da70cd
# Push it to GitHub
git push --set-upstream origin backport-2961-to-8.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.x

Then, create a pull request where the base branch is 8.x and the compare/head branch is backport-2961-to-8.x.