chore(nextjs): add B2B components

[brionmario]

Purpose

This pull request introduces several updates across multiple files, focusing on improving session management, adding theme detection capabilities, enhancing API request handling, and expanding functionality in the JavaScript client. Below is a categorized summary of the most important changes.

Session Management Updates

• Modified the getDecodedIdToken method across multiple files (client.ts, main-thread-client.ts, web-worker-client.ts, authentication-helper.ts, client.ts, web-worker.ts, worker-core.ts) to accept an optional sessionId parameter, enabling session-specific token decoding. [1] [2] [3] [4] [5] [6] [7] [8]

Theme Detection Features

• Added a new themeDetection.ts file that introduces utilities for browser-based theme detection, including methods for detecting theme mode (detectThemeMode), observing class changes (createClassObserver), and listening to media query changes (createMediaQueryListener).
• Exported theme detection utilities from the index.ts file to make them accessible throughout the application.

API Enhancements

• Updated API request handling in multiple files (createOrganization.ts, executeEmbeddedSignInFlow.ts, executeEmbeddedSignUpFlow.ts, getAllOrganizations.ts) to ensure requestConfig is properly spread for better flexibility and customization of headers and other configurations. [1] [2] [3] [4]
• Added logging for errors in the createOrganization function to improve debugging capabilities.

JavaScript Client Updates

• Enhanced the AsgardeoJavaScriptClient class to support optional parameters for methods like getUser, getOrganizations, getCurrentOrganization, and getUserProfile, and added a new method updateUserProfile. These changes improve flexibility and allow session-specific or user-specific operations.

Branding Preference Test Addition

• Added comprehensive tests for the getBrandingPreference API, covering successful fetches, query parameter handling, custom fetchers, error scenarios (invalid URLs, HTTP errors, network errors), and custom headers.

Related Issues

• N/A

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?