SMS MFA message template always uses 'multifactor.otpmessage' instead of 'MultiFactor.OTPMessage'

Hi all,

I'm working on configuring SMS MFA using Twilio in our ServiceNow instance (Yokohama release).

In the MFA provider configuration, I have specified the message key as `MultiFactor.OTPMessage`, and it works well in English.
However, when the user's language is set to Japanese, the message sent via Twilio always uses the translation from `multifactor.otpmessage` (lowercase key), instead of the expected `MultiFactor.OTPMessage`.

Here’s what I’ve confirmed:
- The MFA Provider is correctly configured to use `MultiFactor.OTPMessage` as the message key.
- `sys_translated_text` contains a valid Japanese translation for `MultiFactor.OTPMessage`.
- There is also an old/legacy translation with the key `multifactor.otpmessage`, which was accidentally being picked up and used in the SMS message.

It seems like the system is ignoring the case-sensitive key when resolving translations for non-English languages.

### Question:
Is this a known behavior?
Does ServiceNow fallback to lowercase keys (`multifactor.otpmessage`) even when I explicitly configure `MultiFactor.OTPMessage`?

What is the recommended way to safely prevent the system from using the wrong key without deleting system translation records?

Thanks in advance!