fix: restore RabbitMQ Integration Build workflow configuration

[nookyo]

What type of PR is this? (check all applicable)

• Refactor
• Feature
• Bug Fix
• Optimization
• Documentation Update

Description

This PR introduces a new GitHub Actions workflow “RabbitMQ Integration Build” which is triggered by a custom repository_dispatch event (integration-rabbit-built).

Key functionality added:

• Automatically builds all RabbitMQ integration-related Docker images after the patched RabbitMQ base and management images are published.
• Supports multi-platform builds (linux/amd64, linux/arm64).
• Uses event payload parameters (tag, base_image, management_image, owner, etc.) to dynamically configure image tagging and build arguments.
• Pushes built images to GHCR under the owner specified in event payload.
• Prevents duplicate pipeline runs using concurrency groups.
• Improves release hygiene by retrieving package IDs for cleanup.

This workflow enables automated end-to-end delivery of the RabbitMQ ecosystem in response to custom patched RabbitMQ builds.

• Related Issue #
  [Feat]: Provide continues test of integration for 3rd party forked builds with internal delivery qubership-workflow-hub#439

QA Instructions, Screenshots

No UI changes. To test:

1. Trigger the Build Integration RabbitMQ workflow in the upstream repo.
2. Ensure the custom event dispatch triggers this workflow.
3. Verify that all component Docker images are built successfully and pushed to GHCR.

Breaking Change checklist

If your PR includes any deployment or processing changes, please utilize this checklist:

• Does it change any deployment parameters, logic of their working or rename them?
• Did update from previous version tested with the same set of deployment parameters?

Added/updated tests?

• Yes
• No, and this is why: please replace this line with details on why tests
  have not been included
• I need help with writing tests