Resolve merge conflicts to sync 2.4.9-develop with main

[dshevtsov]

Purpose of this pull request

This pull request (PR) resolves merge conflicts to sync 2.4.9-develop with main.

Summary of what was merged

Conflicts were between HEAD (2.4.9 / devsite) and main (content updates). Resolution keeps devsite conventions (InlineAlert, relative links, ** emphasis) and prefers main where it is more accurate (dynamic db / amqp / stomp resolution, STOMP from 2.4.5, correct filename queue_consumer.xml instead of queue_customer.xml).

Files

1. async-configuration.md

   • Publisher paragraph from main (dynamic connections from env.php).
   • Info alert: main wording + correct filenames + STOMP 2.4.5.

2. bulk-operations-example.md

   • Removed duplicate “Create queue_publisher.xml” heading.
   • Kept explicit <connection name="amqp" exchange="magento" />.
   • Single STOMP publisher example + InlineAlert.
   • Closing note with link to configuration.md and 2.4.5 STOMP.

3. configuration.md

   • main’s full Connection resolution, Handler processing, Consumer spawning, env.php, and ActiveMQ sections.
   • Normalized tables and **For RabbitMQ / STOMP:** labels.

4. index.md

   • main’s MQF overview table + InlineAlert.
   • Switch-to-broker intro from main.
   • Both the product_action_attribute.update RabbitMQ note and an Example: switch a topic to ActiveMQ Artemis (STOMP) block with the inventory.update config from HEAD.

5. migration.md

   • main’s 2.4.4 → 2.4.5+ narrative, shorter tables, Legacy migrations wrapper, em-dash bullets, and 2.4.5+ example labels (dropped “2.4.9 introduced STOMP / backport” wording).

Status

• All conflict markers removed; the five files were staged as part of concluding the merge.