kolla-ansible: Add RabbitMQ 4.2 support and dynamic upgrade paths

The RabbitMQ version check currently hardcodes allowed version jumps.
This makes supporting new major/minor releases (like 4.2) rigid and
requires modifying the core task file.

This commit introduces the `rabbitmq_allowed_upgrades` variable in
the role's defaults. This allows operators to define explicit version
jumps (e.g., 3.13 to 4.2) and makes the upgrade logic more flexible.

The version validation logic now:
1. Checks for standard minor increments (e.g., 4.1 -> 4.2).
2. Checks for explicitly defined jumps in `rabbitmq_allowed_upgrades`.

By moving these definitions to defaults, operators can easily override
them in globals.yml if necessary.

Depends-On: https://review.opendev.org/c/openstack/kolla/+/966017

Change-Id: I0e19cf109eb5665045806b7d925779e82164c2dc
Signed-off-by: Piotr Milewski <vurmil@gmail.com>

0 files changed, 0 insertions, 0 deletions