Stop resolving i18n keys in render props

[brionmario]

Purpose

This pull request updates the @asgardeo/react package to allow consumers to control whether translation strings are resolved or left as i18n keys when using render props. The main change is the introduction of a new option, resolveTranslations, in the flow transformation utilities and their usage in sign-in and sign-up components. This gives more flexibility to consumers who need to handle translations differently, especially in advanced use cases with custom rendering.

Flow transformation and translation handling improvements:

• Added a new resolveTranslations option to the FlowTransformOptions interface and updated the transformComponents and normalizeFlowResponse functions in flowTransformer.ts to support optionally resolving translation strings or keeping i18n keys. [1] [2] [3]
• Updated the SignIn and BaseSignUpContent components to set resolveTranslations: !children, so translations are only resolved when not using render props (i.e., when children is not provided). [1] [2] [3] [4]

Documentation and release notes:

• Added a changeset describing the patch change and the new behavior for render props and i18n resolution.

Related Issues

• feat: provide initial provision for asgardeo/thunder runtime #212

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]

🦋 Changeset detected

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.