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

• https://github.com/wso2/product-is/issues/21004

Related PRs

• N/A

Checklist

• [x] e2e cypress tests locally verified. (for internal contributors)
• [x] Manual test round performed and verified.
• [ ] UX/UI review done on the final implementation.
• [x] 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.