Improve organization user ID and username resolving logics.

[sadilchamishka]

Describe the issue:

The federated users from the organization SSO flow is more towards local user handling rather treating as federated user. Hence improve the codebase to handle the user resolving logics in a proper way.

[sadilchamishka]

• Improve organization SSO user ID resolving logic carbon-identity-framework#5756
• Improve Organization SSO user ID resolving logic to add to the carbon context wso2-extensions/identity-carbon-auth-rest#277
• Fix token revoke issue when org deactivate wso2-extensions/identity-inbound-auth-oauth#2504

[sadilchamishka]

Testing effort.

There are two type of token revocation triggering events can be occurred.

1. From an actions done from root org level.
2. From an actions done from the organization itself.

From an actions done from root org level.

• Deactivate the organization.
  Switched tokens get revoked. Direct SSO admin user tokens get revoked.
• Unshare the b2b app.
  The token against that org and the federated token get revoked.

From an actions done from the organization itself.

• Remove a role from the organization user
  The token against that org get revoked.
• Delete the organization user.
  The token against that org and the federated token get revoked.

[sadilchamishka]

Verified in DEV.
An active sub-organization token was get inactive after disabling the organization.

Screen.Recording.2024-07-02.at.14.49.41.mov