Add missing default ML query descriptions

[lcawl]

Per #2918, where the ML anomaly detection and data frame analytic jobs have an additional bit of info about default queries, that detail is lost since they're re-using the shared QueryContainer description. As a work-around for now I've moved that info into the API description.

[github-actions]

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

API	Status	Request	Response
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_datafeed	🔴	70/71	53/71
ml.put_job	🔴	219/227	223/225

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
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_datafeed	🔴	70/71	53/71
ml.put_job	🔴	219/227	223/225

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
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_datafeed	🔴	70/71	53/71
ml.put_job	🔴	219/227	223/225

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
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_datafeed	🔴	70/71	53/71
ml.put_job	🔴	219/227	223/225

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
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_datafeed	🔴	70/71	53/71
ml.put_job	🔴	219/227	223/225

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
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_datafeed	🔴	70/71	53/71
ml.put_job	🔴	219/227	223/225

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
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_datafeed	🔴	70/71	53/71
ml.put_job	🔴	219/227	223/225

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
ml.put_data_frame_analytics	🔴	32/33	32/33
ml.put_datafeed	🔴	70/71	53/71
ml.put_job	🔴	219/227	223/225

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
ml.put_data_frame_analytics	🟢	33/33	33/33
ml.put_datafeed	🔴	71/71	53/71
ml.put_job	🔴	227/227	223/225

You can validate these APIs 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-2917-to-8.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7cf12f241b76c0c8ca3d864502c65eae5ab38389
# Push it to GitHub
git push --set-upstream origin backport-2917-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-2917-to-8.x.

[github-actions]

The backport to 8.17 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.17 8.17
# Navigate to the new working tree
cd .worktrees/backport-8.17
# Create a new branch
git switch --create backport-2917-to-8.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 7cf12f241b76c0c8ca3d864502c65eae5ab38389
# Push it to GitHub
git push --set-upstream origin backport-2917-to-8.17
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-8.17

Then, create a pull request where the base branch is 8.17 and the compare/head branch is backport-2917-to-8.17.

[lcawl]

💚 All backports created successfully

Status	Branch	Result
✅	8.x

Questions ?

Please refer to the Backport tool documentation

[lcawl]

💚 All backports created successfully

Status	Branch	Result
✅	8.17

Questions ?

Please refer to the Backport tool documentation