feat: Add manifest validation tool

[dimovpetar]

No description provided.

[coveralls]

Pull Request Test Coverage Report for Build 19231440200

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 104 of 110 (94.55%) changed or added relevant lines in 5 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.5%) to 81.841%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/utils/ui5Manifest.ts	46	48	95.83%
src/tools/run_manifest_validation/runValidation.ts	48	52	92.31%

Totals
Change from base Build 19030937854:	0.5%
Covered Lines:	1105
Relevant Lines:	1253

---

💛 - Coveralls

[alexandar-mitsev]

Looks good to me

[alexandar-mitsev]

• now I often get "The MCP validation tool timed out". Seems that it happens mainly if I ask to validate a manifest, complete the task, then edit the manifest and ask to validate again.
  Maybe it is related to the mutex log and cache. Or to the ajv tool itself
  If I restart VS code, the tool can run again without a timeout. Also it runs smoothly couple of times in the same task. But fails with timeout if it runs in two different tasks in the same window.

• every time when I validate manifest _version: "1.60.0" - I get an error
  Error:
  Failed to create UI5 manifest validate function: items value must be ["object","boolean"]

• some older manifests are in the mapping, but have no tag for them, e.g. 1.50.0, 1.45.0
  we should think of how to improve the tool to handle this. Maybe suggest an upgrade in that case as well?

• there are many logs for format "uri" ignored and format "uri-reference" ignored in the console, but this is not an error. Can be resolved with later update