Document permissions api

[artandor]

Proposed Changes

This PR try to answer the issue exposed in #774 I documented the permissions required for every API route in order to have a clear overview of the required permissions when checking the documentation.

Types of Changes

What types of changes does your code introduce to this project? Put an x in the boxes that apply

• [ ] Bugfix (non-breaking change which fixes issue #NNNN)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [x] Documentation (correction or otherwise)
• [ ] Cosmetics (whitespace, appearance)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask on the mailing list. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [x] I have read the CONTRIBUTING.md document
• [x] I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
• [x] All tests pass locally with my changes
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added necessary documentation (if appropriate)
• [ ] Any dependent changes have been merged and published in related repositories

[michaelklishin]

We could use two columns for tags and object permissions. I don't have a strong opinion about this but it will enforce more structure on future contributors. Free form text would not.

[dcorbacho]

@artandor The management plugin has been moved to the server repository. Please re-submit your PR against this repository once you have applied the requested changes.

Many thanks for your contribution!