[Issue] Fix for communication.xml Handlers merging processs

[m2-assistant]

This issue is automatically created based on existing pull request: #28926: Fix for communication.xml Handlers merging processs

---

Description (*)

This changes fixes the "handler" merging process into communication.xml files which currently overrides all the handlers with the last one created, ignoring it's different names as expected. Issue found during custom handler development for MCOM module where there was already a handler for a message.

Manual testing scenarios (*)

1. Develop a module which defines two handlers, with different names, for a same request on communication.xml
2. Check config after flush cache, it will only includes the last handler specified.

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)
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @engcom-Delta. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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.

[magento-engcom-team]

✅ Confirmed by @engcom-Delta
Thank you for verifying the issue. Based on the provided information internal tickets MC-39141 were created

Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #28926 by @matiashidalgo in 2.4-develop branch
Related commit(s):

• fb9f52daa532b4020a9cb5a805ab1e2df87560d5
• 2cbb726956d9e0481deeb99de348e6af769ea2ea
• 11ccb291f24c23b6c2602bfcdc44c096ada7e14b
• 623e87faf718164fe26a6b1315e9f3dd444d2fdd
• d5680d23fb7938e5e780d8cf0d90710fc5c5aac7
• cf9de17dad689a1922cc987ed484bd7d84e91009
• 8e054c7e5c84b3057d17ab34594b3911745c9c91
• e7cde72591b81895e8b02e1de3e8f88a4ede80b1
• 90e457d983e906f361f9c1a994382383a8c20131
• 1bf790a4ca2be7fa255c8173132bb47134021def
• c373f3efb47469313d02bce7811bfa7e38e3e941
• 0cfb88ad329cb1e1db929dd798d8641269157a5a
• be308faf3a6927ae8546ed7cbee002924f56dc70

The fix will be available with the upcoming 2.4.3 release.