CAMEL-23648: Update container version workflow to regenerate metadata.json

[davsclaus]

Summary

• Add update-metadata-version.py script to update serviceVersion in metadata.json files when container image versions are bumped
• Update check-container-versions.yml workflow to call this script and include the regenerated metadata.json files in each commit

After CAMEL-23643 added serviceVersion to metadata.json (extracted from container image tags), the container version upgrade workflow needs to also update these generated files when bumping container.properties — otherwise CI detects stale generated files and fails the automated PRs.

The Python script matches entries by artifactId and old serviceVersion to update only the affected entries, and produces output matching Jackson's DefaultPrettyPrinter format so the result is identical to what the Maven build generates.

Test plan

• Round-trip formatting test: update + revert produces identical output to original
• Multi-entry module test: AWS (16 entries) all updated, Kafka entries unaffected
• Both metadata.json files (test-infra-all and catalog) tested

Claude Code on behalf of Claus Ibsen

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.