MFA "next token" mode is not supported

Describe the bug
ZAAS authentication provider does not support MFA in the RSA "next token" mode. The user is unable to log in when it happens. The only option is to use some other authentication service to reset the authentication process to normal mode.

attempt 1 - 401:

"messageContent": "The request has not been applied because it lacks valid authentication credentials. Invalid username or password",

attempt 2 - 401:

"messageContent": "The request has not been applied because it lacks valid authentication credentials. Invalid username or password",

It is not supported by z/OSMF. The ticket with IBM / z/OSMF team is opened. It will require additional work on the APIML side afterward to handle messages and response codes correctly.

Documentation:

https://techdocs.broadcom.com/us/en/ca-mainframe-software/security/ca-advanced-authentication-mainframe/2-0/using-with-ca-top-secret/manage-multi-factor-authentication-credentials-ca-top-secret/sign-on-when-using-rsa-securid-while-in-next-token-mode-ca-top-secret.html

https://www.ibm.com/docs/en/zos/2.3.0?topic=SSLTBW_2.3.0/com.ibm.zos.v2r3.azfu100/azf_task_tsonexttoken.htm

Related conversation:
#1600

Start by reviewing the RSA SecurID “next token” behavior described in the issue and the related conversation in #1600. Check the open IBM/z/OSMF ticket before investigating the APIML authentication flow. Done means APIML handles the relevant messages and response codes after z/OSMF support is available.