Fix rabbit-queues check

This check had 3 issues. The first is that it was checking again :min
and not :expected, hence would always fail.  Similarly, there is no
fall-through case when > 0 and not within the critical threshold.

Also adding a -i argument so that we can quiet down some noisy queues -
in particular, q-plugin.
Differentiate between critical and warning

Right now the rabbit queues check is broken in that it only fires
criticals and is checking the wrong parameter for the high water mark.
Update this check to provide both warnings and criticals.
Increase MySQL maximum connections
be more lenient about token expiration

we were killing tokens that may have been in use. while that logic is
certainly correct, there may be transactions in flight. and, to be
super safe, give a very long reprieve interval of 1 day. this keeps the
token database clean and gives us some runway.
Merge pull request #420 from craigtracey/tokentimeout

be more lenient about token expiration
Merge pull request #419 from blueboxgroup/mysql-max-connections

Increase MySQL maximum connections
Updating changelog for 0.9.2
Merge pull request #421 from blueboxgroup/0.9.2-changelog

Updating changelog for 0.9.2
Merge pull request #415 from craigtracey/rabbitqueues

Fix rabbit-queues check