Release Report Enhancements (#1750)

[daveoconnor]

This PR is related to ticket #1750.

Changes:

• Adds PDF generation of release reports with a new ReleaseReport model, and a draft+publish process w/ option to override to immediately publish.
• Adds PDF generation as final step in "Do It All" for release tasks.
• Minor: Adds LOCAL_DEVELOPMENT to celery docker compose config to enable pycharm debugger use.
• Minor: Updates pycharm debugger libs versions.
• Minor: fixes some invalid markup in the release report html.
• Minor: Adds some missing steps to local hyperkitty db setup.

Chromium was used because weazyprint doesn't support javascript, which we need for the charts.

Testing:

1. 1. With a functioning ReportConfiguration set up, generate a release report as usual. In the admin UI confirm a report has been created in your local media folder under media/release-reports, which has a datetime value appended to the path. Pay attention the modification times of all files.
   2. In the admin UI check "published" and save, this should rename the file to remove the datetime value, saving it like release-report-boost-1-89-0.pdf
   3. Start a new release report process, confirm both files exist after creation. Publishing optional.
   4. Start a new release report process after checking off "Publish". This should overwrite the previous published release-report-boost-1-89-0.pdf.
2. Under "Versions" in the admin UI click "do it all" and confirm that a new release report has been created.

For the PDFs confirm all fonts and data match what the previous traditional PDF generation process using the browser print dialog looked like.

Note:

1. It's probably a good idea to keep an eye on the logs to confirm things are happening.
2. Release report records are generated when the PDF generation begins and won't necessarily have a file name associated when you first check the admin list if it's too soon after the process has started, so you may need to give it a few minutes until the process has completed for the name to appear.

[karimarie67]

@gregjkal @rbbeeston Can you guys (or guy) please review? Thank you!

[rbbeeston]

I'm good with this if Greg approves