RabbitMQ: model the new tls field (upstream cozystack#2683) #42

cozystack/cozystack#2683 adds a tls object to packages/apps/rabbitmq/values.schema.json:

tls:
  enabled: bool                 # no default, absent means off
  disableNonTLSListeners: bool  # no default, absent means plaintext listeners stay open

The provider models tls for postgres, kafka, nats and qdrant but not for rabbitmq, so a cozystack_rabbitmq resource cannot set it.

Two things to carry over from the chart's own validation rather than invent: disableNonTLSListeners is refused when enabled is not true, and it is refused together with users or vhosts because the broker-level switch drops the in-cluster clients those create. The chart rejects both at render time, so a provider-side validator would only make the error earlier and clearer. Neither field carries a schema default; model both optional with no Default:.

Enabling TLS also moves the metrics port from 15692 to 15691, which matters to anything the provider exposes about the release's endpoints.