[Issue] Add queue consumers start chain command

[m2-assistant]

This issue is automatically created based on existing pull request: #40840: Add queue consumers start chain command

---

Adds bin/magento queue:consumers:start-chain command.

Description (*)

This allows you to run many specified queue consumers in one command, without manually running each.

I've split the cron running up into two parts: app/code/Magento/MessageQueue/Model/Cron/ConsumersRunner.php and app/code/Magento/MessageQueue/Model/ConsumersRunnerExecutor.php. This allows to make the other command to chain queue consumers.

The problem it solves

One of our clients is hosted on PlatformSH. PlatformSH won't work with the queue consumers running in the cron: https://github.com/platformsh-templates/magento2ce/blob/master/deploy.php#L136

Issue is, the worker runs async.operations.all, which seems to require a queue connection which we don't have, but we require DB queues to still work. With this, We can safely run the same cron runner, that works for us without a queue connection through a worker that wont break platformsh.

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes magento/magento2#<issue_number>

Manual testing scenarios (*)

Pretty minimal, but run test with crons and running the new command,

Questions or comments

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)

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-17316 is successfully created for this GitHub issue.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @Sam-Mear,

Thanks for your reporting and collaboration.

We gone through with the description and seems to be an enhancement to proceed further marking this as a Feature Request.

Thanks.