chore: fix and align dependencies across different packages

[colinscz]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

• Align used minimal Typescript version
• Update Angular 20.x minor version used in demo app to latest to resolve vulnerability findings
• Update React demo app dependencies
• Update outdated dependencies

📝 Checklist

• I have linked an issue or discussion.
• It's submitted to the main branch
• When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
• I have updated the documentation accordingly.
• All tests are passing
• New/updated tests are included
• I have updated the "upcoming" section inside docs/changelog.md explaining the changes I contributed

If adding a new feature, the PR's description includes:

• A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

[pennal]

In general. I think this is fine. What I am noticing though is that we havent yet decided on how we want to declare dependencies, whether we want to pinpoint them or we want to allow some freedom to the package manager.

[pennal]

Why are you rolling these back? According to https://react.dev/blog/2025/12/11/denial-of-service-and-source-code-exposure-in-react-server-components we should be using >=19.1.3 or 19.2.2

[pennal]

In both the react and vue packages you are not pinpointing versions, which you are doing in angular. Is there a reason for this?