#2274: add GitUrlUpdater

[cap-juan]

This PR fixes #2274

Implemented changes:

• Added GitUrlUpdater for the git tool with the single git edition.
• Added automatic detection and mapping of Git for Windows versions such as 2.55.0(3) to IDEasy version format 2.55.0.3.
• Added download URLs for Windows x64 and ARM64 installers.
• Added tests for Git URL generation and version mapping.
• Linux and macOS are intentionally not handled via ide-urls: Git is normally installed there through the native package manager/system tooling rather than by downloading a standalone installer. ide-urls is therefore only required for the Windows installer artifacts.

---

Testing instructions

Please add conscise, understandable instructions on how a reviewer can test/verify the functionality of your contribution here:

1. Run the Git updater test:
   mvn -pl url-updater -Dtest=GitUrlUpdaterTest test

2. Verify that the test succeeds and creates URL metadata for both Windows architectures:

windows_x64
windows_arm64

3. Optionally run the URL updater locally against an ide-urls checkout and verify that Git metadata is generated below:
   ide-urls/git/git/<version>/ (this takes very long time and I tested already locally as the image shows)

---

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

[coveralls]

Coverage Report for CI Build 31470088553

Coverage increased (+0.03%) to 72.913%

Details

• Coverage increased (+0.03%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• 17 coverage regressions across 1 file.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

17 previously-covered lines in 1 file lost coverage.

File	Lines Losing Coverage	Coverage
com/devonfw/tools/ide/url/updater/UpdateManager.java	17	0.0%

---

Coverage Stats

Relevant Lines:	17567
Covered Lines:	13357
Line Coverage:	76.03%
Relevant Branches:	7755
Covered Branches:	5106
Branch Coverage:	65.84%
Branches in Coverage %:	Yes
Coverage Strength:	3.23 hits per line

---

💛 - Coveralls