#1456 : Fix uninstall via windows settings bug

[KarimALotfy]

This PR fixes the Windows uninstall flow for IDEasy when uninstalling from Apps/Installed apps.

This PR fixes #1456

Implemented changes:

• The MSI uninstall action now runs from the installed folder and logs correctly, and the CLI uninstall no longer fails when cleaning up on Windows because it now uses the actual bash.exe path instead of the bare bash command. This resolved a failure during uninstall from Apps.

---

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

[coveralls]

Coverage Report for CI Build 25330206019

Coverage increased (+0.02%) to 70.662%

Details

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

Uncovered Changes

No uncovered changes found.

Coverage Regressions

5 previously-covered lines in 1 file lost coverage.

File	Lines Losing Coverage	Coverage
com/devonfw/tools/ide/tool/IdeasyCommandlet.java	5	72.32%

---

Coverage Stats

Relevant Lines:	15353
Covered Lines:	11306
Line Coverage:	73.64%
Relevant Branches:	6850
Covered Branches:	4383
Branch Coverage:	63.99%
Branches in Coverage %:	Yes
Coverage Strength:	3.11 hits per line

---

💛 - Coveralls

[hohwille]

@KarimALotfy thanks for your PR. You properly analysed and fixed the problem. 👍
Indeed on Windows the bash is typically not on the PATH variable and that could have caused the error.
Also you now follow the same approach as we do in the install step and this makes it also more robust.
E.g. if the user manually deleted the log directory this would have caused the uninstall to fail.

Could you please add the issue to our CHANGELOG for the currently release (see DoD)?

BTW: since we are using single quotes to embed the script logic into XML you do not have to escape double quotes with ". However, nothing is wrong with that. This escaping only makes it even uglier to read - stupid idea actually to use XML syntax for such things since this && encoded as && cannot be prevented and all this makes it hard to maintain. I guess you already had your personal fun editing this file and testing the results.
Great job that you made it!