#1981: fix ide update failing on windows arm64

[cap-juan]

This PR fixes #1981

Implemented changes:

• Added a fallback from windows-arm64 to windows-x64 when no native Windows ARM64 snapshot artifact is available.
• Added snapshot metadata inspection to verify which platform classifiers are actually published.
• Added short-term caching for Maven metadata to avoid downloading and parsing the same maven-metadata.xml multiple times.
• Kept the fallback limited to Windows ARM64 so that Linux and macOS artifact resolution remain unchanged.
• Added tests covering the ARM64 fallback, existing ARM64 artifacts, unsupported classifiers, and snapshot-version resolution.

Testing instructions

1. Run the focused Maven repository tests:
   mvn -pl cli -Dtest=MvnRepositoryTest test

2. Run the complete test suite:
   mvn clean test

3. Build and install the modified IDEasy version locally:
   ./build-local-dev.sh

4. Open a new PowerShell session and simulate Windows ARM64:
   $env:IDE_OPTIONS = "-Dos.arch=arm64"

5. Verify the simulated architecture:
   ide status

6. Run the previously failing snapshot upgrade:
   ide upgrade --mode=snapshot

7. Verify that IDEasy falls back to the windows-x64 artifact instead of failing with a 404 for windows-arm64.

8. Remove the architecture override after testing:
   Remove-Item Env:IDE_OPTIONS -ErrorAction SilentlyContinue

---

Checklist for this PR

Make sure everything is checked before merging this PR. For further info please also see
our DoD.

• When running mvn clean test locally all tests pass and build is successful
• PR title is of the form #«issue-id»: «brief summary» (e.g. #921: fixed setup.bat). If no issue ID exists, title only.
• PR top-level comment summarizes what has been done and contains link to addressed issue(s)
• PR and issue(s) have suitable labels
• Issue is set to In Progress and assigned to you or there is no issue (might happen for very small PRs)
• You followed all coding conventions
• You have added the issue implemented by your PR in CHANGELOG.adoc unless issue is labeled
  with internal
• You have formulated clear instructions on how to test your contribution under "Testing instructions"

Checklist for tool commandlets

Have you added a new «tool» as commandlet? There are the following additional checks:

• The tool can be installed automatically (during setup via settings) or via the commandlet call
• The tool is isolated in its IDEasy project, see Sandbox Principle
• The new tool is added to the table of tools in LICENSE.asciidoc
• The new commandlet is a command-wrapper for «tool»
• Proper help texts for all supported languages are added here
• The new commandlet installs potential dependencies automatically
• The variables «TOOL»_VERSION and «TOOL»_EDITION are honored by your commandlet
• The new commandlet is tested on all platforms it is available for or tested on all platforms that are in scope of the linked issue