fix: expose reInitialize from @asgardeo/react & @asgardeo/nextjs

[brionmario]

Purpose

This pull request introduces a new method, reInitialize, across the Asgardeo JavaScript SDK clients (core, React, and Next.js) to allow dynamic re-initialization of the client with a partial configuration. This enables updating configuration fields without a full re-initialization, improving flexibility for applications that need to update authentication settings at runtime. The method is added to the core client interface, implemented in the React and Next.js clients, and exposed through the relevant context/provider layers.

Core SDK Enhancements:

• Added the reInitialize abstract method to the core AsgardeoJavaScriptClient class and the AsgardeoClient interface, allowing clients to be re-initialized with partial configuration updates. [1] [2]

Next.js SDK Updates:

• Implemented the reInitialize method in AsgardeoNextClient, including error handling and return value, and exposed it via the server utility in asgardeo.ts. [1] [2] [3]

React SDK Updates:

• Implemented the reInitialize method in AsgardeoReactClient with loading state management and error handling.
• Added reInitialize to the AsgardeoContextProps type and provided it in the default context and through the AsgardeoProvider, making it available to React consumers. [1] [2] [3]

Related Issues

• Fixes fix: option to re-initialize the SDK on the fly is not exposed #180

Related PRs

• N/A

Checklist

• e2e cypress tests locally verified.
• Manual test round performed and verified.
• UX/UI review done on the final implementation.
• Documentation provided. (Add links if there are any)
• Unit tests provided. (Add links if there are any)
• Integration tests provided. (Add links if there are any)

Security checks

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