Add support for configuring missingQueuesFatal property

[nosan]

see gh-14122

[snicoll]

Thanks again @nosan, please review the polish commit if you can.

[nosan]

@snicoll I wanted to implement this in a similar way, but I haven't done because of the javadoc meanings. Could you please check one more time the difference between simple/direct missing-queues-fatal, just to make sure everything is ok :)

Simple , Direct

Thanks in advance.

[snicoll]

I've noticed those but it delegates to AbstractRabbitListenerContainerFactory so I don't think that mapping in the sub-classes was the right call.

As for having two properties, this is an interesting question. I've paged @garyrussell for some more opinion.

[garyrussell]

When true, if the queues are removed while the container is running, the containeris stopped.

This difference is because of the internal design of the containers.

With the SMLC, each consumer instance can listen to multiple queues; if any one of those queues is deleted from the broker; the consumer is killed by the broker.
With the new container (Direct), there is a consumer for each queue, so deleting one queue doesn’t affect the other consumer(s).

[snicoll]

Alright, let's document that as two keys. I'll push another polish later today

[snicoll]

@nosan thank you very much for drawing my attention to this. I thought that the property was common since it was calling the abstract factory but it turns out that there is a subtle semantic difference that we have to explain. I took the opportunity to revisit this a bit further by exposing the difference in default values (rather than keeping `Boolean).