Add userId in successful user-registration response.

[AfraHussaindeen]

Proposed changes in this pull request

• $Subject
• Resolves Expose userId in the result HTML page after successful self-registration. wso2/product-is#22275

To be merged after

• Introduce ResolvedUser class wso2/carbon-identity-framework#6297

Checklist (for reviewing)

General

• Is this PR explained thoroughly? All code changes must be accounted for in the PR description.
• Is the PR labeled correctly?

Functionality

• Are all requirements met? Compare implemented functionality with the requirements specification.
• Does the UI work as expected? There should be no Javascript errors in the console; all resources should load. There should be no unexpected errors. Deliberately try to break the feature to find out if there are corner cases that are not handled.

Code

• Do you fully understand the introduced changes to the code? If not ask for clarification, it might uncover ways to solve a problem in a more elegant and efficient way.
• Does the PR introduce any inefficient database requests? Use the debug server to check for duplicate requests.
• Are all necessary strings marked for translation? All strings that are exposed to users via the UI must be marked for translation.

Tests

• Are there sufficient test cases? Ensure that all components are tested individually; models, forms, and serializers should be tested in isolation even if a test for a view covers these components.
• If this is a bug fix, are tests for the issue in place? There must be a test case for the bug to ensure the issue won’t regress. Make sure that the tests break without the new code to fix the issue.
• If this is a new feature or a significant change to an existing feature? has the manual testing spreadsheet been updated with instructions for manual testing?

Security

• Confirm this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets.
• Are all UI and API inputs run through forms or serializers?
• Are all external inputs validated and sanitized appropriately?
• Does all branching logic have a default case?
• Does this solution handle outliers and edge cases gracefully?
• Are all external communications secured and restricted to SSL?

Documentation

• Are changes to the UI documented in the platform docs? If this PR introduces new platform site functionality or changes existing ones, the changes should be documented.
• Are changes to the API documented in the API docs? If this PR introduces new API functionality or changes existing ones, the changes must be documented.
• Are reusable components documented? If this PR introduces components that are relevant to other developers (for instance a mixin for a view or a generic form) they should be documented in the Wiki.

[codecov]

Codecov Report

Attention: Patch coverage is 38.46154% with 8 lines in your changes missing coverage. Please review.

Project coverage is 48.90%. Comparing base (4ea5d99) to head (e6a6846).
Report is 42 commits behind head on master.

Files with missing lines	Patch %	Lines
.../identity/user/endpoint/impl/MeApiServiceImpl.java	0.00%	8 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##             master     #907      +/-   ##
============================================
- Coverage     50.83%   48.90%   -1.93%     
- Complexity     2426     2524      +98     
============================================
  Files           298      300       +2     
  Lines         17885    19015    +1130     
  Branches       2553     2868     +315     
============================================
+ Hits           9091     9299     +208     
- Misses         7649     8538     +889     
- Partials       1145     1178      +33     

Flag	Coverage Δ
unit	38.74% <38.46%> (+0.33%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jenkins-is-staging]

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/12863847891

[jenkins-is-staging]

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/12863847891
Status: cancelled

[jenkins-is-staging]

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/12871841163

[jenkins-is-staging]

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/12871841163
Status: cancelled

[jenkins-is-staging]

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/12879949097

[jenkins-is-staging]

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/12879949097
Status: success

[jenkins-is-staging]

Approving the pull request based on the successful pr build https://github.com/wso2/product-is/actions/runs/12879949097