Use user language for messages and errors in Forgot Password feature (frontend)

[teosarca]

Is this a bug or feature request?

follow-up of #1878
backend: metasfresh/metasfresh-webui-api-legacy#1038

What is the current behavior?

Which are the steps to reproduce?

• try to reset your password; click on the URL you got in your email
• check how the backend is called:
  

i.e.

• the GET /availableLanguages is called => at this point we don't know user's language
• the GET /messages is called => at this point we don't know user's language
• the GET /resetPassword/{token} is called => now here we are setting session's language using user's language
  .....

What is the expected or desired behavior?

• instead of GET /resetPassword/{token} please use POST /resetPassword/{token}/init (see http://w101.metasfresh.com:8080/swagger-ui.html#/login-rest-controller endpoints).
• always call POST /resetPassword/{token}/init before getting the /messages because that POST will initialize session's language.

[siemiatj]

This is going to be tricky the way things are laid out now. Translations are the first request, so probably easiest thing to do would be duplicating this request on enter action for reset password views.

[teosarca]

i could live with that....
(talking about requesting again the messages)

[metas-dh]

Results of IT1
tested in release

User language is correcly considered in Forgot Password feature:

• user had de_DE set: Accept-Language set in Frontend: de_DE: OK
• user had en_US set: Accept-Language set in Frontend: en_US: OK