Describe the bug

RabbitMQ itself allows user passwords with # in. In Cluster Operator deployed RMQ, default user creds are configured using RMQ configuration files which treats # as start of a comment. This bug is reported in: rabbitmq/default-user-credential-updater#42

Note that the golang ini that the default-user-credential-updater uses is not a blocker here. It allows # in value if you quote it with backtick. However, there is no equivalent string escaping from RMQ (cuttlefish).

Additional context

We could look into change the way how default user password being configured for vault integrated cluster. Current problem lies with no escaping with conf files. RMQ itself allows # in user passwords. If the operator can load default user credential through importing definition, or some other way that does not have constraint with special characters, that would solve this issue.