Added password reset service email config. Using this config for gett…

[vlmed]

Description (*)

I have created new following configs:

1. Stores->Configuration->Customer->Customer Configuration->Password Options->Password Reset Service Email.
   

This config allows change email in the We received too many requests for password resets. Please wait and try again later or contact hello@example.com message. This message appears when customer requested few times password reset.

2. Stores->Configuration->Advanced->Admin->Security->Password Reset Service Email.
   
   This config allows change email in the We received too many requests for password resets. Please wait and try again later or contact hello@example.com message. This message appears when admin user requested few times password reset.
   

I created a new configurations because I think it's a bad idea to use a configuration from the Magento Contact module.

Fixed Issues (if relevant)

1. Fixes Password reset error message references hello@example.com which cannot be changed unless contact form is enabled #32837

Manual testing scenarios (*)

Scenario 1. Reset Customer password

1. Change email in the config Stores->Configuration->Customer->Customer Configuration->Password Options->Password Reset Service Email. For example (test@example.com)
   

2. On the password reset route (/customer/account/forgotpassword/) request a password reset multiple times. Assuming out-of-the-box configuration you will eventually get the error message that contain email from previous step:
   We received too many requests for password resets. Please wait and try again later or contact test@example.com
   

Scenario 2. Reset Admin password

1. Change email in the config Stores->Configuration->Customer->Customer Configuration->Password Options->Password Reset Service Email. For example (test1@example.com)
   

2. On the password reset route (admin/auth/forgotpassword/) request a password reset multiple times. Assuming out-of-the-box configuration you will eventually get the error message that contain email from previous step:
   We received too many requests for password resets. Please wait and try again later or contact test1@example.com
   

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @vlmed. Thank you for your contribution
Here are some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE,
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[vlmed]

@magento run all tests

[vlmed]

@magento run all tests

[Den4ik]

Hi @vlmed Thanks for you contribution

As I see this changes can't be merged into the patch release, because improving admin interface.
I agree with this improvements, but looks like this changes should be approved by Product Owner the first

[vlmed]

@magento run Functional Tests EE, Functional Tests B2B

[vlmed]

@magento run Functional Tests B2B

[magento-automated-testing]

No builds to run for your request.

[Den4ik]

@magento run Functional Tests EE, Functional Tests B2B

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[Den4ik]

@magento run Functional Tests EE, Functional Tests B2B

[magento-automated-testing]

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please re-request them if they don't show in a reasonable amount of time.

[Den4ik]

@magento-engcom-team Could someone assist with this PR?