Add a back to draft capability for published reports

[anilsonmez-simsoft]

Admins now can unpublish reports from the client-side using the Unpublish Report button at the bottom of the report page. This function needs to be enabled in the anet-dictionary.yml by setting canUnpublishReports to true.

Closes #3480

User changes

• none

Super User changes

• none

Admin changes

• If enabled in the dictionary, admins can unpublish (i.e. put back to draft) published reports.
• Note that admins can now also manually publish future engagement reports that have been approved (previously they couldn't, and these would only get automatically published after the quarantine period).

System admin changes

• anet.yml or anet-dictionary.yml needs change
  If admins should be able to unpublish reports, add this setting to the dictionary:

  fields:
    report:
      canUnpublishReports: true
  

• db needs migration
• documentation has changed
• graphql schema has changed
  There's a new GraphQL mutation, unpublishReport

Checklist

• Described the user behavior in PR body
• Referenced/updated all related issues
• commits follow a repo#issue: Title title format and these 7 rules
• commits have a clean history, otherwise PR may be squash-merged
• Added and/or updated unit tests
• Added and/or updated e2e tests
• Added and/or updated data migrations
• Updated documentation
• Resolved all build errors and warnings
• Opened debt issues for anything not resolved here