More honest reset password request response

[joshtrichards]

• Resolves: UX: Forgot password form should trim user input #37408

Summary

(Addresses feedback in additional comments of #37408)

Makes the response provided to users requesting a password reset more honest. Also reminds users to verify the provided account name or email address. Removes redundant copy. Continues to do so without leaking information.

TODO

• Review

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[Valdnet]

Change "administrator" to "administration".

[artonge]

Nitpick, but nice otherwise 👍

[szaimen]

Hi @joshtrichards please squash, rebase, run npm ci and npm run build and commit the changes here which will allow us to merge this. Thank you!

Done

[jtrees]

LGTM. Thanks!

[joshtrichards]

Hi @joshtrichards please squash, rebase, run npm ci and npm run build and commit the changes here which will allow us to merge this. Thank you!

Done - theoretically. I never got it to pass the GH node workflow check 100% here in the PR (and with my latest push it's waiting on approval to run again).

Since the comp'd assets get stashed in the commit it appears the GH node.yml workflow builds them again and diffs them. They always come up different than fail. Is that how it's supposed to work? Am I doing something wrong? Do they get rebuilt again during the final merge on your side?