3.13.0 - 3.13.2: Wrong warning messages that dead letter messages get dropped

[ansd]

Describe the bug

In RabbitMQ 3.13, RabbitMQ outputs wrong and misleading warning messages such as

[warning] <0.1162.0> Message dropped. Dead-letter queues cycle detected: <<"a2">>
[warning] <0.1162.0> This cycle will NOT be reported again.

even though there was no dead-letter cycle and no message was dropped.

Reproduction steps

Check logs of the following test case https://github.com/rabbitmq/rabbitmq-server/blob/46e1058f318a8312344bbdd9fa0d6e97f481c7a9/deps/rabbit/test/dead_lettering_SUITE.erl#L381-L437

However, much simpler scenarios will also incorrectly log warnings.

Expected behavior

RabbitMQ should only output this warning, if RabbitMQ dropped the message because an actual cycle occurred.

Additional context

No response