[maven,typescript] (#332, #462, #463) Update dependencies to latest package versions

[deyan-r]

Description

Typescript projects were updated to require Node.js 20+(node>=20.18.1, npm>=10.8.2)
All dependencies were updated to the latest versions.
Where needed, the code was updated to be compatible with changes in components interfaces.
Such alignment includes, but not limited to:

• all: update dependencies to latest versions and resolve minor issues
• polyglotpkg: fs-extra and globby were replaced by fs
• vropkg: updated according new uuid and unzipper api; minor differences in expected files
• vrotest: fs-extra was replaced by fs
• vrotsc: few changes in expected js code generated by the latest version of tsc

Polyglot archetype to set proper runtime values in polyglot.json for sample vro templates.
A few bugs encountered were fixed.

Checklist

• I have added relevant error handling and logging messages to help troubleshooting
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation, relevant usage information (if applicable)
• I have updated the PR title with affected component, related issue number and a short summary of the changes introduced
• I have added labels for implementation kind (kind/) and version type (version/)
• I have tested against live environment, if applicable
• I have synced any structure and/or content vRA-NG improvements with vra-ng and ts-vra-ng archetypes (if applicable)
• I have my changes rebased and squashed to the minimal number of relevant commits. Notice: don't squash all commits
• I have added a descriptive commit message with a short title, including a Fixed #XXX - or Closed #XXX - prefix to auto-close the issue

Testing

Testing included three steps:

1. Build components and entire BTVA (unit and integration tests passed)
2. Archetype lifecycle testing: create, build, push, pull
3. Build and push existing vra/vro projects

Release Notes

Update typescript projects to node.js 20+ and latest versions of dependencies

Related issues and PRs

#463
#462
#332 (duplicated by #464)

[vmwclabot]

@deyan-r, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit fdc0d47 must be signed by [email protected]
• Commit d06191f must be signed by [email protected]
• Commit 494dc02 has a no-reply/unreachable author email address: [email protected]
• Commit 8ba5b72 has a no-reply/unreachable author email address: [email protected]
• Commit c4ebbef has a no-reply/unreachable author email address: [email protected]
• Commit daf1ae5 must be signed by [email protected]
• Commit b07d980 must be signed by [email protected]
• Commit d13b372 must be signed by [email protected]
• Commit 3fb1986 has a no-reply/unreachable author email address: [email protected]
• Commit 04dba04 has a no-reply/unreachable author email address: [email protected]
• Commit 7df4004 must be signed by [email protected]
• Commit 130730c must be signed by [email protected]
• Commit a4ca895 must be signed by [email protected]
• Commit 19cf11f has a no-reply/unreachable author email address: [email protected]
• Commit 665f7c2 must be signed by [email protected]
• Commit 366008a must be signed by [email protected]
• Commit 4696928 must be signed by [email protected]
• Commit 41d3a60 must be signed by [email protected]
• Commit a967248 must be signed by [email protected]
• Commit 35c0863 must be signed by [email protected]
• Commit 98bfe1f must be signed by [email protected]
• Commit 3ecbd55 must be signed by [email protected]
• Commit 5b79a31 must be signed by [email protected]
• Commit 246f789 must be signed by [email protected]

[vmwclabot]

@deyan-r, you must sign every commit in this pull request acknowledging our Developer Certificate of Origin before your changes are merged. This can be done by adding Signed-off-by: John Doe <[email protected]> to the last line of each Git commit message. The e-mail address used to sign must match the e-mail address of the Git author. Click here to view the Developer Certificate of Origin agreement.

• Commit fdc0d47 must be signed by [email protected]
• Commit d06191f must be signed by [email protected]
• Commit 494dc02 has a no-reply/unreachable author email address: [email protected]
• Commit 8ba5b72 has a no-reply/unreachable author email address: [email protected]
• Commit c4ebbef has a no-reply/unreachable author email address: [email protected]
• Commit daf1ae5 must be signed by [email protected]
• Commit b07d980 must be signed by [email protected]
• Commit d13b372 must be signed by [email protected]
• Commit 3fb1986 has a no-reply/unreachable author email address: [email protected]
• Commit 04dba04 has a no-reply/unreachable author email address: [email protected]
• Commit 7df4004 must be signed by [email protected]
• Commit 130730c must be signed by [email protected]
• Commit a4ca895 must be signed by [email protected]
• Commit 19cf11f has a no-reply/unreachable author email address: [email protected]
• Commit 665f7c2 must be signed by [email protected]
• Commit 366008a must be signed by [email protected]
• Commit 4696928 must be signed by [email protected]
• Commit 41d3a60 must be signed by [email protected]
• Commit a967248 must be signed by [email protected]
• Commit 35c0863 must be signed by [email protected]
• Commit 98bfe1f must be signed by [email protected]
• Commit 3ecbd55 must be signed by [email protected]
• Commit 5b79a31 must be signed by [email protected]
• Commit 246f789 must be signed by [email protected]

[VenelinBakalov]

Nice that's quite some effort put in this one! I will try to get help with reviewing this PR soon. We will for sure need a Release.md entry with the changes you described in the PR description and also a suggested Upgrade procedure because of the major change of the node version. Let me first discuss internally how to handle that and then we can update the PR.