Supporting API based authentication for sub organization based on current B2B architecture

[AnuradhaSK]

Describe the issue:
This issue to track the tasks required to support API based authentication for sub organization based on current B2B architecture.

1. If the root application is marked as an API based authentication enabled application, inherit that configuration for shared apps as well
2. If the root application is marked as a public client, inherit that configuration for shared apps as well
3. Improve organization login authenticator to bypass sending client secret to sub org token request if the shared app is created as a public client. (similar to: https://github.com/wso2-extensions/identity-auth-organization-login/compare/main...AnuradhaSK:identity-auth-organization-login:api-based?expand=1)
   May we can additional config when it is executed in API based auth flow
4. Client ID unification per tenant feature gaps #20324 this bug fix might required as this was required when trying manually updating shared app's oauth2 client properties manually to doing the PoC

Try out
Upon fixing the codes, the following API collection should work without executing [FIX NEEDED].. folder's requests
API based Auth for Sub Orgs.postman_collection.json