More rebust Request Queue Menu structure

[#1]

At present the request Menu structure has some serious drawbacks. It is entirely tied to project and queue setup settings. I find it to be very limiting.

Some of the drawbacks are

• All requests in a topic have to expose the same fields. This is restrictive. I find that I have to enable fields that don't make sense just because another request needs to have that field exposed. This causes noise and confusion.
• To make an Email enabled request you have to create it at the project level. Anyone with permissions to email the queue will also see it in the request menu. This clutters up the menu.

I'd like the hierarchy of the request menu to be designable by business process and navigation needs and then mapped to the correct request form.