Upgrade wagtail to 2.15.4

[johnnyporkchops]

Summary

Upgrade wagtail to 2.15.4

• Resolves Upgrade Wagtail to 2.15.4 LTS #4807
  Also resolves [Snyk: Low] wagtail Information Exposure (Due: 4/27/2022) #5043

Please check these upgrade-considerations notes and see if anything needs attention and add to "Items to check" list below.

• 2.12 Release upgrade-considerations
• 2.13 Release upgrade-considerations
  • 2.13.5 Release upgrade-considerations
• 2.14 Release upgrade-considerations
  • 2.14.2 Release upgrade-considerations
• 2.15 Release upgrade-considerations
  • 2.15.2 Release upgrade-considerations (N/A - related to Support for SQLite )

Items to check from all upgrade considerations above:

• Updated handling of non-required StreamFields

  • check models.py and blocks.py

• Determine how/if we use wagtail search backend or elastic search?

  • Removed support for Elasticsearch 2 @patphongs Does this effect us?
  • New database search backend (I don't think this effects us (?))

---

Some new features/changes since 2.11.9:

• Easier to change admin color scheme
• stream_data is now deprecated when we access streamfields in the Python shell( can use page.body[0].block_type or raw_data
  https://docs.wagtail.org/en/stable/releases/2.12.html#stream-data-on-streamfield-values-is-deprecated
• End of Internet Explorer 11 support (Just for admin, not live site)
• Typed table block
  Would have to be enabled, not available in admin out of box. Possibly coming soon for Wagtail wishlist: Control column widths on table blocks #4258
• Commenting (no configuration required )

###Related issues:
QA ticket: #5132

Required reviewers

Two frontend, QA ticket done by content team

Impacted areas of the application

modified: ../requirements.txt

Screenshots

---

How to test

This has been merged to dev for Content team to test: https://dev.fec.gov/admin , QA ticket: #5132

Will be merged by 04/12 so further testing can take place on dev/stage

Before merging:

• Get latest database dump for Wagtail database
• Remove feature deploy task in tasks. py before merging

Test:

• checkout branch and pip install -r requirements.txt
• cd fec, ./manage.py migrate
• test Wagtail admin, creating pages, uploading images, documents
• test editing existing pages
• does anything look awry in the admin ?

[codecov-commenter]

Codecov Report

Merging #5148 (615dc1c) into develop (e57c821) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop    #5148   +/-   ##
========================================
  Coverage    74.93%   74.93%           
========================================
  Files          125      125           
  Lines         8120     8120           
  Branches       648      648           
========================================
  Hits          6085     6085           
  Misses        2035     2035           

Impacted Files	Coverage Δ
fec/home/models.py	88.16% <ø> (ø)

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e57c821...615dc1c. Read the comment docs.

[kathycarothers]

I was not able to test the admin part. I did test creating a new page, adding a document, adding buttons etc. When I tried to add a picture it showed it was there, but the picture did not come up. It might be because I choose an old picture in feature. All seemed to be working well. @johnnyporkchops

[johnnyporkchops]

Thanks for your quick review @kathycarothers. I don't think we'll see the images in feature b/c it's not mapped to an S3.
cc: @patphongs is that correct?

[patphongs]

@johnnyporkchops Everything looks good with the upgrade. The only thing that we discussed was changing the MeetingPage.imported_html model to use StreamFieldPanel to get rid of the warning. Even though that particular field we don't use, it would be better to not have a warning on migrations or app start up.

Also I don't believe we are using ElasticSearch, so we should be good there.

[patphongs]

👍 Good to go, thanks @johnnyporkchops

[rfultz]

LGTM—haven't figured out how to break it