[UserProfile] Enable self-service profile updates in JavaScript SDKs

[janithjay]

Current Limitation

Currently, self-service profile updates do not work end-to-end. The SDK attempts to retrieve and save profile modifications using a /scim2/Me endpoint that the backend does not support (as there are no SCIM2 endpoints in the product).

To resolve this, the profile read and update flows must be transitioned to the backend's native /users/me endpoint.

[janithjay]

• Fixed this for the react sdk in #9.
• Corrected the self-service profile update path from the non-existent SCIM2 /scim2/Me endpoint to the existing PUT /users/me API.
• Profile data fetching was also changed to use GET /users/me as the default source. Previously as default method, it fetched from OIDC ID token decoding.
• This needs to be reverted back to defaulting on the OIDC ID token for fetching profile data, with a new configuration option added, so users can choose the fetch method either from the OIDC ID token claims or from the GET /users/me endpoint.

[janithjay]

When implementing the configuration option to choose the source of profile attributes (either OIDC ID token or GET /users/me API), the following challenge and proposed plan should be noted,

The Problem with OIDC Token Source

• If the profile attributes are retrieved purely from the OIDC ID token, required attributes (such as username or other mandatory keys) might not be configured to be sent in the ID token from the Console.
• When a user attempts to edit and save a profile attribute, the PUT /users/me request fails validation because the backend schema requires these missing attributes to be present in the PUT payload.

Proposed Plan

• Default Source (GET /users/me): Default the user attributes retrieval to the GET /users/me endpoint. This guarantees all backend attributes (including required ones) are loaded, ensuring inline edits and updates work seamlessly.
• OIDC Token Source as Read-Only: If the user configures the SDK to resolve attributes solely from the OIDC ID token claims, the profile interface should default to read-only mode. Disabling inline edits in this mode prevents validation failures on fields that are missing in the OIDC payload.