Make resolve conflict in transport version its own task

[rjernst]

This commit moves the action for resolving merge conflicts in transport version files a separate task instead of a command line flag to generate.

[elasticsearchmachine]

Pinging @elastic/es-core-infra (Team:Core/Infra)

[github-actions]

🔍 Preview links for changed docs

• docs/internal/Versioning.md

[github-actions]

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel

[mark-vieira]

FWIW, if we made this an Action then we could make applying this to tasks slightly more ergonomic. Such as:

Action<MyTask> commonConfig = t -> { t.setGroup("foo") };
project.getTasks.register("myTask", MyTask.class, commonConfig).configure { 
  // unique config 
};

or

project.getTasks.register("myTask", MyTask.class, t -> {
  // unique config
}.configure(commonConfig);

Pick your preferred style.

[rjernst]

I forgot about this, I'll do it the next time I tweak this file.

[elasticsearchmachine]

💔 Backport failed

Status	Branch	Result
❌	8.19	Commit could not be cherrypicked due to conflicts
❌	9.1	Commit could not be cherrypicked due to conflicts
❌	8.18	Commit could not be cherrypicked due to conflicts
❌	9.0	Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 134842