Improve handler queue naming

[sweetlandj]

Currently handler queues are named by taking the MD5 hash of the handler type name. This is done to ensure that the queue names:

• Are short enough to not run afoul of path length restrictions in Windows
• Are unique (enough)
• Are consistent across restarts

We need to continue to meet the above goals while addressing the following:

• Queue names should be descriptive
• Queue names should be intuitive
• Queue names should be discoverable/navigable

Possible solutions:

• Change the default to use the Type.Name (not Type.FullName) truncated at a certain number of characters with a small(er) hash of the full name to ensure uniqueness
• Introduce a [Queue] attribute for the HandleMessage method(s) that indicates the queue name, max concurrency, max retries, etc. for queues used for handling rules targeting those methods