CONTINUE_SIGN_IN_WITH_MFA_SETUP_SELECTION challenge is not triggered.

### Before creating a new issue, please confirm:

- [x] I have [searched for duplicate or closed issues](https://github.com/aws-amplify/amplify-ui/issues?q=is%3Aissue+) and [discussions](https://github.com/aws-amplify/amplify-ui/discussions).
- [x] I have tried disabling all browser extensions or using a different browser
- [x] I have tried deleting the node_modules folder and reinstalling my dependencies
- [x] I have read the guide for [submitting bug reports](https://github.com/aws-amplify/amplify-ui/blob/main/CONTRIBUTING.md#bug-reports).

### On which framework/platform are you having an issue?

React

### Which UI component?

Authenticator

### How is your app built?

Vite

### What browsers are you seeing the problem on?

Chrome

### Which region are you seeing the problem in?

_No response_

### Please describe your bug.

I have a userPool with **Required MFA**, and the MFA methods are **TOTP and SMS**.
When the user tries to signIn, amplify should return the challenge **CONTINUE_SIGN_IN_WITH_MFA_SETUP_SELECTION**, but the amplify's response is
**CONTINUE_SIGN_IN_WITH_TOTP_SETUP**

Please let us know, when **CONTINUE_SIGN_IN_WITH_MFA_SETUP_SELECTION** challenge is triggered (if there are any further configs required).

### What's the expected behaviour?

I have a userPool with **Required MFA**, and the MFA methods are **TOTP** and **SMS**.
When the user tries to signIn, amplify should return the challenge **CONTINUE_SIGN_IN_WITH_MFA_SETUP_SELECTION**.

### Help us reproduce the bug!

Create a user Pool with **Required MFA** and add **TOTP** and **SMS** as MFA methods.
signIn with username and password through aws-amplify.

### Code Snippet

```typescript
// Put your code below this line.

```

### Console log output

_No response_

### Additional information and screenshots

_No response_

Start by reproducing the sign-in flow in a React/Vite app with a user pool requiring MFA and supporting TOTP and SMS. Trace the signIn entry point and challenge handling to determine why CONTINUE_SIGN_IN_WITH_TOTP_SETUP is returned instead of CONTINUE_SIGN_IN_WITH_MFA_SETUP_SELECTION; done means the documented configuration produces the correct challenge and regression coverage verifies it.

Written by the indexing model from the issue text.