fix: enable utilities and accessibility features

[ludtkemorgan]

This PR addresses #4440 #4439

• Addresses the issue in full
• Addresses only certain aspects of the issue

Description

Listing utilities and accessibility features functionality already exist. However it was not working correctly. This PR fixes all of the bugs as well as connecting it to the new feature flag functionality

NOTE: the jurisdiction table fields have also been removed since we can now use the feature flag table

How Can This Be Tested/Reviewed?

Both feature flags are added to the staging seeded data for "Bloomington" jurisdiction so the following can be tested with a new reseed

• Create a new listing in partners for the "Bloomington" jurisdiction.
  • Verify that the Utilities checkbox section and the accessibility features checkbox section appear
  • Verify that you can select specific utilities and accessibility features. On save make sure they are saved correctly
• Edit the listing and change the utilities/accessibility features
  • Verify that the fields are correctly updated on save
• Create a new listing not for "Bloomington" jurisdiction and verify that the two sections don't appear
• Go to the public site and verify that the first listing created shows the correct utilities and accessibility features on the listing details page

Author Checklist:

• Added QA notes to the issue with applicable URLs
• Reviewed in a desktop view
• Reviewed in a mobile view
• Reviewed considering accessibility
• Added tests covering the changes
• Made corresponding changes to the documentation
• Ran yarn generate:client and/or created a migration when required

Review Process:

• Read and understand the issue
• Ensure the author has added QA notes
• Review the code itself from a style point of view
• Pull the changes down locally and test that the acceptance criteria is met
• Either (1) explicitly ask a clarifying question, (2) request changes, or (3) approve the PR, even if there are very small remaining changes, if you don't need to re-review after the updates

[netlify]

✅ Deploy Preview for partners-bloom-dev ready!

Name	Link
🔨 Latest commit	28bc43b
🔍 Latest deploy log	https://app.netlify.com/sites/partners-bloom-dev/deploys/6789407bcc0d240008aa03f8
😎 Deploy Preview	https://deploy-preview-4503--partners-bloom-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for bloom-exygy-dev ready!

Name	Link
🔨 Latest commit	28bc43b
🔍 Latest deploy log	https://app.netlify.com/sites/bloom-exygy-dev/deploys/6789407b5a6bc10008e8bd15
😎 Deploy Preview	https://deploy-preview-4503--bloom-exygy-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[YazeedLoonat]

looks good, one small 🧹

[mcgarrye]

issue: signed in as an admin, I can still see the sections for a listing for another jurisdiction on creation

Screen.Recording.2025-01-07.at.3.22.30.PM.mov

[ludtkemorgan]

@mcgarrye good catch. I was missing an s and it now works correctly so is ready for re-review

[emilyjablonski]

This feels like a very niche use case, but if I take a listing that has both utilities and a11y features, and then change the jurisdiction to be one that doesn't include them, the listing keeps the data. Otherwise looks great!

I also think the spacing above the utilities here is too big, and the text size is small enough to be considered inaccessible in the bulleted list - could we increase it a bit? Is there a design for what this should look like in core?

[ludtkemorgan]

@emilyjablonski There is no design for this as these fields already existed in both public and partners, there was just some bugs with the saving of the values. So the design is the same as when it was implemented 3 years ago. Looks like that styling is coming from a ui-components component AdditionalFees.

[emilyjablonski]

@ludtkemorgan I'm about to rewrite that section, so it's no worries to me!

[emilyjablonski]

🐧