Fix verbose: true not sending when only flowId is present

[brionmario]

Purpose

This pull request refactors the embedded sign-in and sign-up flows in the @asgardeo/javascript package to improve payload handling. The main change is to ensure the verbose parameter is only added internally and conditionally, making the API usage cleaner and more predictable.

Embedded flow payload handling improvements:

• Both executeEmbeddedSignInFlowV2 and executeEmbeddedSignUpFlowV2 now strip out any user-supplied verbose parameter from the payload to prevent external control over this internal flag. (packages/javascript/src/api/v2/executeEmbeddedSignInFlowV2.ts, [1]; packages/javascript/src/api/v2/executeEmbeddedSignUpFlowV2.ts, [2]
• The verbose: true parameter is now conditionally added only when the payload contains either just applicationId and flowType, or just flowId. This ensures that the meta field is included in the response only when necessary. (packages/javascript/src/api/v2/executeEmbeddedSignInFlowV2.ts, [1]; packages/javascript/src/api/v2/executeEmbeddedSignUpFlowV2.ts, [2]

Documentation:

• Added a changeset describing the refactor and rationale for the changes. (.changeset/hungry-ties-bet.md, .changeset/hungry-ties-bet.mdR1-R6)

Related Issues

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

Related PRs

• Add support to resolve component metadata from Thunder Flow APIs #285

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.