Purpose

This pull request introduces improvements to how persisted and session data are managed across the JavaScript and React SDKs, with a focus on handling the applicationId and cleaning up the use of browser storage for configuration. The changes add a new persisted data store, ensure applicationId is retained across sessions, and simplify how configuration is managed and accessed in React components.

Persisted Data Store and Application ID Handling:

• Added a new PersistedData store type in the Stores enum to retain data such as applicationId across sessions and application restarts. (packages/javascript/src/models/store.ts)
• Implemented getPersistedData and setPersistedData methods in StorageManager to read and write to the new persisted data store. (packages/javascript/src/StorageManager.ts)
• Updated AsgardeoAuthClient to store and retrieve applicationId in the persisted data store, ensuring it is available even if not provided in the config on subsequent loads. (packages/javascript/src/__legacy__/client.ts)

React SDK Configuration and Storage Cleanup:

• Removed the use of sessionStorage for storing platform and baseUrl in the React provider and related logic, relying instead on the configuration object directly. (packages/react/src/contexts/Asgardeo/AsgardeoProvider.tsx, packages/react/src/AsgardeoReactClient.ts) [1] [2] [3]
• Updated the React context to use applicationId from the config, ensuring consistency and reflecting the new persisted data approach. (packages/react/src/contexts/Asgardeo/AsgardeoProvider.tsx)

Related Issues

• Refreshing the Thunder Gate breaks the flow thunder-id/thunderid#1886
• Refactor storage values that breaks Multi Instance behaviours #411

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?