Restrict adding second-factor authenticators in the initial login step

[NipuniBhagya]

Purpose

This PR adds support to restrict the second-factor authenticators like iProov, Duo, etc. in the first step of the login flow when orchestrating the flow using the login flow composer.

Related Issues

• Restrict Adding Second-Factor Authenticators in Initial Login Step product-is#21004

Related PRs

• N/A

Checklist

• e2e cypress tests locally verified. (for internal contributors)
• Manual test round performed and verified.
• UX/UI review done on the final implementation.
• Documentation provided. (Add links if there are any)
• Relevant backend changes deployed and verified
• Unit tests provided. (Add links if there are any)
• Integration tests provided. (Add links if there are any)

Security checks

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

[wso2-jenkins-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.