[DO NOTE MERGE] Zebra stripes by election and hide dropdown option

[johnnyporkchops]

Summary (required)

NOTE: To avoid conflicts, please merge this related PR first: #6512

• Resolves Zebra Stripes in Reporting Dates Table Template Not Operating without Supporting Code #6583
• Give editors of ReportngDatesTable template more granular comtrol over Zebra striping by enabling the ability to add custom classes to rows in the table block.
  • Specifically for pages where the editor wants to manually stripe by election-name instead of the default -- by state.
• A new checkbox to to hide the states dropdown on the template instead of having to add CSS the template in an HTML block.

Required reviewers

one dev and @djgarr - ( I can push to feature when you are ready)

Impacted areas of the application

zebra striping options ReportingDatesTable templates
States dropdown on ReportingDatesTable templates

How to test

I can push to feature when you are ready to test @djgarr

• npm run build-js
• Open an existing or create a new page using Reporting dates table template
• Edit a cell in the State column to wrap the election name in a custom <election> html tag, like:
  • Example:<election class="fl1">Florida 1st Congressional District Special Primary</election>
• Preview or publish the page to confirm that the class was added to that row:
  • Example result in browser: <tr class="fl1 fl">
• Test that footnotes still work for these cells to by putting "~1" at the very end of the content in that cell
• Test linked election names by wrapping the <election>tag in an <a> link tag
  • Example: <a href="https://www.fec.gov/help-candidates-and-committees/dates-and-deadlines/2024-reporting-dates/prior-notices-2024/election-report-notice-florida/"><election class="fl1">Florida 1st Congressional District Special Primary</election></a>

System architecture updates (if applicable)

(If this pull request changes our current system diagram, include a description of those changes here and create a new ticket to update the system diagram)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 79.91%. Comparing base (8a7a79d) to head (25784e6).
Report is 24 commits behind head on develop.

Additional details and impacted files

@@           Coverage Diff            @@
##           develop    #6597   +/-   ##
========================================
  Coverage    79.91%   79.91%           
========================================
  Files          235      235           
  Lines         5147     5148    +1     
========================================
+ Hits          4113     4114    +1     
  Misses        1034     1034           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[rfultz]

Being help text, can we lowercase 'Tip', remove an i from includiing, add an 'n' in 'cotrol', and change tilda ) to tilde). As a nice touch, I'd like to monospace the code in help_text but it doesn't seem like Wagtail supports that. Yet?

I'd want to verify with Content that the help text addresses questions they may have.

[johnnyporkchops]

@rfultz I definitely see how this might seem like overkill. But this template is only used by one team member now and becomes increasingly esoteric with each iteration. So I want to be explicit about this non-intuitive functionality for the current user and the eventual new user, someday.

[rfultz]

❤️

[johnnyporkchops]

Closing in favor of PR to release