Remove autocommand from vendored dependencies

[Kielek]

Summary of changes

Raise the minimum jaraco.text version to 4.3.0 and regenerate the complete vendored dependency closure.

Updated:

• jaraco.text 4.0.0 -> 4.3.0
• jaraco.context 6.1.0 -> 6.1.2
• jaraco.functools 4.4.0 -> 4.6.0
• more-itertools 10.8.0 -> 11.1.0
• packaging 26.0 -> 26.3
• tomli 2.4.0 -> 2.4.1
• wheel 0.46.3 -> 0.47.0

Added:

• annotated-doc 0.0.5
• colorama 0.4.6
• markdown-it-py 4.2.0
• mdurl 0.1.2
• Pygments 2.20.0
• rich 15.0.0
• shellingham 1.5.4
• typer 0.27.1
• typer-slim 0.24.0

Dropped:

• autocommand 2.2.2
• importlib_metadata 8.7.1
• platformdirs 4.4.0
• zipp 3.23.0

backports.tarfile remains at 1.2.0 and was refreshed with the rest of the vendored tree.

Assisted-by: Codex

Closes #5049

Pull Request Checklist

• Changes have tests - already existings
• News fragment added in newsfragments/.
  (See documentation for details)

[Kielek]

In https://github.com/open-telemetry/opentelemetry-demo/ we have setuptools as indirect dependency. It brings also autocommand which is problematic. It will be great to fully remove it from the chain. It is the easiest way, the hard part is to document usage and ask CNCF team for the exception for usage.

Please let me know what do you think about these changes. I know that the PR contain a lot of changes, but I do not see possibility to make the changes small.

[Copilot]

Copilot wasn't able to review this pull request because it exceeds the maximum number of files (300). Try reducing the number of changed files and requesting a review from Copilot again.

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[ngoldbaum]

A 200k LoC diff seems pretty large! Did you see #5256 where I tried to do this? Do you understand where the huge diff is coming from?

[Kielek]

@ngoldbaum, I have seen your PR. It is not solving licensing-chain problem. It still references autocommand.

If we speaking about 200k Loc changes. I agree that it is huge, but it should be managable by the maintainers. If I would to accept this kind of changes, I would repeat exercise from scratch. If there will be no differences, I would accept such PR. The only additional condition is if you are fine with the new dependency chain.