Use pnpm catalogs in identity-apps repository

[brionmario]

Is your suggestion related to an experience? Please describe.

Currently, we declare dependencies in each feature's package.json file within the identity-apps repository rather than consolidating them in the root package.json.

This approach offers certain advantages:

• It allows individual features to be modular, making it easier to move them out of the monorepo if needed.
• It improves readability by clearly identifying dependencies needed for each feature.
• It can simplify bundling with tools like Rollup.

However, this approach has several drawbacks:

1. Multiple versions of the same package: Version conflicts can arise, especially if different versions of a package (e.g., mixing ~ and ^ or strict versioning) are declared across different features.
2. Local development issues: Local environment inconsistencies can lead to errors that aren’t caught in development, due to variations in package versions across features.

Describe the improvement

Integrate pnpm catalogs and use the catalog protocol to centralize common dependencies. This will help streamline package management and minimize potential version conflicts. Key packages that can be managed with catalogs include:

• @asgardeo/auth-react
• @oxygen-ui/react
• @wso2is packages (both features and modules)

Additional context

N/A