fix: update peer dependencies to allow compatible versions

[kavindadimuthu]

Purpose

This pull request updates the peer dependency version requirements across several package manifests to use semver ranges instead of exact versions. This change allows for greater compatibility with future versions of dependencies, making it easier for consumers to use newer releases without running into version conflicts.

Dependency versioning updates:

• Changed peer dependencies in packages/react/package.json, packages/react-router/package.json, packages/tanstack-router/package.json, packages/nextjs/package.json, and packages/__legacy__/react/package.json to use >= semver ranges for react, @types/react, react-router, @tanstack/react-router, packages/express/package.json, packages/vue/package.json, next, express and vue instead of exact versions.

Related Issues

• bug: getting an error while installing @asgardeo/react with npm #269 - bug: getting an error while installing @asgardeo/react with npm

Related PRs

• N/A

Checklist

• Followed the CONTRIBUTING guidelines.
• Manual test round performed and verified.
• Documentation provided. (Add links if there are any)
• Unit tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

[asgardeo-github-bot]

⚠️ No Changeset found

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go.

If these changes should result in a version bump, you need to add a changeset.

Refer Release Documentation to learn how to add a changeset.