See #5957. HTTP api to generate hashed password from cleartext password

[SimonUnge]

Proposed Changes

HTTP api to generate hashed password. See #5957

Types of Changes

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

• Bug fix (non-breaking change which fixes issue #NNNN)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause an observable behavior change in existing systems)
• Documentation improvements (corrections, new content, etc)
• Cosmetic change (whitespace, formatting, etc)
• Build system and/or CI

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.

• I have read the CONTRIBUTING.md document
• I have signed the CA (see https://cla.pivotal.io/sign/rabbitmq)
• I have added tests that prove my fix is effective or that my feature works
• All tests pass locally with my changes
• If relevant, I have added necessary documentation to https://github.com/rabbitmq/rabbitmq-website
• If relevant, I have added this change to the first version(s) in release-notes that I expect to introduce it

Further Comments

Current 'solution' generates the hashed password with a GET, with the password in the URI: /auth/hash_password/some_password

But, perhaps it would be better with a POST and a payload, i.e {password, }?

Easy to fix, this is mainly to get comments on what approach you prefer. And what URI to use as well!
@lukebakken

[michaelklishin]

@SimonUnge can you please rebase this PR?