Refactor branding preference fetching logic

[kavindadimuthu]

Purpose

This pull request updates the branding preferences logic in the SDK to ensure branding is only fetched and applied when explicitly enabled, rather than by default. The changes clarify the documentation and adjust the code to require inheritFromBranding to be set to true for branding to be fetched.

Branding preferences logic update:

• Updated the documentation for the inheritFromBranding property in the ThemePreferences interface to clarify that branding is only fetched when explicitly enabled, and defaults to false.
• Changed the branding fetch logic in AsgardeoProvider to only fetch branding when preferences.theme.inheritFromBranding is true, rather than when it is not false.
• Updated the enabled prop for branding in AsgardeoProvider to require preferences.theme.inheritFromBranding to be true.

Related Issues

• Fixes Gracefully handle branding preferences API call error message in React SDK #384

Related PRs

• N/A

Checklist

• Followed the CONTRIBUTING guidelines.
• Manual test round performed and verified.
• Documentation provided. (Add links if there are any)
• Unit tests provided. (Add links if there are any)

Security checks

• Followed secure coding standards in http://wso2.com/technical-reports/wso2-secure-engineering-guidelines?
• Confirmed that this PR doesn't commit any keys, passwords, tokens, usernames, or other secrets?

[asgardeo-github-bot]

⚠️ No Changeset found

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go.

If these changes should result in a version bump, you need to add a changeset.

Refer Release Documentation to learn how to add a changeset.