Configure UpdateForV10 tag with eslint-plugin-jsdoc

[pquentin]

We sometimes want to make breaking changes but have to wait until the next major version. To not forget about those, this commit introduces an UpdateForV10 JSDoc tag that can be used in any comment. There are a few benefits of using JSDoc instead of a simple TODO comment:

• With the allowlist of tags in our ESLint config, we can't make typos
• We enforce a proper description to explain why the breaking change needs to be made

Note that this tag has the same name as the Elasticsearch UpdateForV10 annotation, which will prove useful when the Elasticsearch specification becomes part of the Elasticsearch repository in the future.

Since we're now using https://github.com/gajus/eslint-plugin-jsdoc, this pull request also applies a number of useful fixes.

[github-actions]

Following you can find the validation changes against the target branch for the APIs.

No changes detected.

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

[JoshMock]

LGTM!

[github-actions]

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

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

[github-actions]

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

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