[PRODSEC-11289] Fix Angular i18n vulnerable to CSS

[nikita-web-ua]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x")

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation
• Other... Please describe:

What is the current behaviour? (You can also link to an open issue here)

https://github.com/Alfresco/alfresco-ng2-components/security/dependabot/364

What is the new behaviour?

Does this PR introduce a breaking change? (check one with "x")

• Yes
• No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...

Other information:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

Updates Angular patch versions to address a reported i18n-related security vulnerability (CSS injection) flagged by Dependabot, keeping the workspace on a consistent Angular 19.2.19 patch level.

Changes:

• Bump Angular runtime dependencies from 19.2.18 to 19.2.19 (animations/common/compiler/core/forms/platform-browser/platform-browser-dynamic/router).
• Bump @angular/compiler-cli from 19.2.18 to 19.2.19.
• Regenerate package-lock.json to reflect the updated Angular package tarballs, peer deps, and integrity hashes.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File	Description
package.json	Updates Angular package versions to 19.2.19 to address the security alert.
package-lock.json	Syncs lockfile entries (versions/resolved/integrity/peer deps) with the Angular 19.2.19 update.