Removed CliIndexerReindexActionGroup action group usage for modules (mix)

[sergiy-v]

Description

Removed usage or changed value of CliIndexerReindexActionGroup action group for the following modules: Elasticsearch, Elasticsearch6, LayeredNavigation, LoginAsCustomer, Newsletter, UrlRewrite, Weee, Wishlist

Resolved issues:

1. resolves [Issue] Removed CliIndexerReindexActionGroup action group usage for modules (mix) #31852: Removed CliIndexerReindexActionGroup action group usage for modules (mix)

[m2-assistant]

Hi @sergiy-v. Thank you for your contribution
Here is 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

[sergiy-v]

@magento create issue

[sergiy-v]

@magento run all tests

[sergiy-v]

@magento run Functional Tests CE

[sergiy-v]

@magento run Functional Tests EE,Functional Tests B2B,Semantic Version Checker

[sergiy-v]

@magento run Functional Tests B2B

[sergiy-v]

@magento run Functional Tests B2B

[sergiy-v]

@magento run Functional Tests B2B

[sergiy-v]

@magento run WebAPI Tests, Unit Tests, Static Tests, Sample Data Tests EE, Sample Data Tests CE, Sample Data Tests B2B, Magento Health Index, Integration Tests, Database Compare

[sergiy-v]

Everything are green, @rogyar please proceed with review.

[magento-engcom-team]

Hi @rogyar, thank you for the review.
ENGCOM-8796 has been created to process this Pull Request
✳️ @rogyar, could you please add one of the following labels to the Pull Request?

Label	Description
Auto-Tests: Covered	All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered	Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required	Changes in Pull Request does not require coverage by auto-tests

[engcom-Alfa]

QA not applicable

[m2-assistant]

Hi @sergiy-v, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.