Log Message:
Update net/rabbitmq to 3.5.3.

RabbitMQ 3.5.3:
- If rabbitmqctl can't contact a node, suggest to verify any Erlang TLS
  distribution configuration
- Ensure the memory monitor is fully started before the file handle cache
  is used
- Management plugin: Fix a crash during RabbitMQ startup if
  force_fine_statistics is set in rabbitmq_management_agent configuration

RabbitMQ 3.5.2:
- Improve integration with Docker
- Add a way to send log messages (both "normal" and sasl messages) to \ 
stdout
- Do not try to use exec before su ... as su(1) forks a process anyway
- Report a queue is under flow control only if it was in this situation
  in the last 1 second, instead of the last 5 seconds previously
- Add a check to ensure the Mnesia directory is not shared with the PID file
  location or the plugin expansion directory
- Ensure the file handle cache remains under the memory high watermark
  when syncing a mirrored queue
- Restore support for messages stored on disk with the previous x-death
  header format
- Ensure passwords containing $ characters are properly escaped so they are
  not interpreted by the shell, when a password is changed using rabbitmqctl
  change_password
- Management plugin: Allow to configure rates_mode even if only
  rabbitmq-management-agent is enabled
- Management plugin: Fix a badarith crash if for some reasons, the disk free
  space or the file descriptors count are temporarily reported incorrectly
- STOMP plugin: Ensure the "processor" thread is terminated at the \ 
same time
  the "reader" thread exits

RabbitMQ 3.5.1:
- Introduce a new channel log category for channel log messages
- Ensure consumer_closed events are emitted for the actually closed channels
  only, not all of them
- Ensure the number of x-death message headers doesn't grow indefinitely
- Adjust the file read buffer cache size to avoid useless reads
- Ensure the priority queue plugin reports its memory consumption properly
- Prevent a crash while synchronising paged out priority queues
- Pass the PID file to rabbitmqctl stop in rabbitmq-server.ocf, exactly
  like Debian- and Red Hat-flavour init scripts
- AMQP plugin: Fix heartbeats
- AMQP plugin: Respond with a protocol error if a disposition frame
  is incorrect
- AMQP plugin: Fix a crash if the initial-delivery-count is not 0