[Task]: Developers can request a new content review to re-enable their listing via the API

[eviljeff]

Description

Similar to #15989 a developer should be able to use the AMO API to discover what his listing is rejected for, and to request a new review.

Acceptance Criteria

• developer can query the API (for add-ons they are a developer of) to return details of their listing content rejection
• developer can request a new review of the listing content via the API (for add-ons they are a developer of)

┆Issue is synchronized with this Jira Task

[ioanarusiczki]

Wfm with https://reviewers.addons-dev.allizom.org/en-US/reviewers/review-content/640692 and I tried to look into details but forgot the Content review queue, I'll try again and get back with final results.

[ioanarusiczki]

I played some more with the two endpoints and I've noticed some stuffs today.

The PATCH request is throwing a 202 Response "The response has been received but has not been acted upon" even with the has_requested_review=True but that's not a big deal, the problem would be that when I'm sending values such as " " 3 empty spaces or any other string value "esfgbrrtntyn" while "can_request_review" is true -> the API response interprets it as "true" and has_requested_review becomes true in the response.

An example with a screenshot -> I tried this with "has_requested_review" as form-data or adding it into a JSON body (got the same results)

And after content is approved the GET response would keep the information of "policies" field

I'm going to file the first problem noticed.