Allow developer requests for new content review

[eviljeff]

Fixes: mozilla/addons#15989

Description

Adds a button for the developer to request a new review after they have made changes to their content, with the rejection reasons exposed.

Context

I implemented this on top of the existing visibility selector - my thinking was that saying the listing is "visible" when the listing was rejected was wrong - we'd want to say Rejected there - so why not also include the rejection details there too. Better UX would be great...

Testing

• Content Listing Reject in reviewer tools, and see the rejection details with a button in developer hub. on the (Status & )Versions page.
  • if you include comments they should be exposed too.
• Press the request review button; see it's now disabled (it's just feedback to the developer we got the request - hitting it multiple times wouldn't do anything)
• See the add-on is now back in the content review queue
• if you content approve it then add-on should revert to it's state prior to content rejection.

Checklist

• Add #ISSUENUM at the top of your PR to an existing open issue in the mozilla/addons repository.
• Successfully verified the change locally.
• The change is covered by automated tests, or otherwise indicated why doing so is unnecessary/impossible.
• Add before and after screenshots (Only for changes that impact the UI).
• Add or update relevant docs reflecting the changes made.