Upgrade cuttlefish to 3.1.0

[lukebakken]

Related to https://github.com/rabbitmq/opportunities/issues/207

[lukebakken]

Here is how I tested on Linux:

• Create a generic unix package from this branch.
• Clone this repository: https://github.com/lukebakken/rabbitmq-server-6041
• cd to that clone, and run setup.sh. It'll generate the correct rabbitmq.conf and rabbitmq-env.conf files for you.
• Start the generic unix package this way:

  RABBITMQ_CONF_ENV_FILE="/path/to/rabbitmq-env.conf" ./sbin/rabbitmq-plugins enable rabbitmq_management rabbitmq_top
  LOG=debug RABBITMQ_ALLOW_INPUT=true RABBITMQ_CONF_ENV_FILE="/path/to/rabbitmq-env.conf" ./sbin/rabbitmq-server
  

• Visit https://localhost:15671 to verify HTTPS
• Connect an AMQPS client to the server, or use openssl:

  openssl s_client -host localhost -port 5671 -CAfile './RabbitMQ Sérvér - Евгений/certs/ca_certificate.pem'
  

• Investigate the output and log files to ensure there aren't any lists of integers or mis-encoded unicode strings. You may still see a few that will be resolved in my next PR to convert all ~s and ~p formats to their unicode equivalent.
• Click around the management UI to ensure no 500s are returned, and that strings look correct
• Create a vhost named using strings with non-ASCII, non latin characters, like RabbitMQ Sérvér/Евгений. I also used Евгений for the description and a tag value like Евгений, foo bar baz , Sérvér, which correctly ends up as three tags:

  $ ./sbin/rabbitmqctl list_vhosts name tags
  Listing vhosts ...
  name    tags
  /       []
  RabbitMQ Sérvér/Евгений [Евгений, foo bar baz, Sérvér]
  

[michaelklishin]

Works as advertised:

Although per AMQP 0-9-1 spec, entity names are supposed to be ASCII. But directories with
Latin and Russian Cyrillic characters are accepted from rabbitmq.conf just fine 👍👍