Improve Messaging & UX in the event of Keycloak error

[keileyo]

In the event that there is a keycloak error such as the one below, we would prefer that this didn't just say please try again later. We should let the user know that we have been notified of the error and are working on the resolution. Likely need further team (especially UX) disucssion on this one.

emailSendErrorMessage=Failed to send email, please try again later.

missingParameterMessage=Missing parameters: {0}
clientNotFoundMessage=Client not found.
clientDisabledMessage=Client disabled.
invalidParameterMessage=Invalid parameter: {0}

[awolfe76]

@keileyo @lesgou @designlanguage - any thoughts here about what we would like to say with these messages?

[keileyo]

Per conversations, for beta, the action that we want to take is to tell the user to come back later. I think something similar to the 503 in 536 makes sense.

@designlanguage @awolfe76 thoughts?

"We're sorry, the HMDA platform is currently unavailable. Please try logging in again later. If this problem persists, contact HMDA help."

[keileyo]

Just reiterating sprint priorities, this is not a must have for launch.