fix: untranslate non-english preferences in db

[ludtkemorgan]

Pull Request Template

Issue Overview

This PR addresses bloom-housing#3856

• This change addresses the issue in full
• This change addresses only certain aspects of the issue
• This change is a dependency for another issue
• This change has a dependency from another issue

Description

Multiselect questions that have a comma, period, or apostrophe were not getting properly untranslated back to english in order to get sent back to the backend. The fix for that has already been released, but this is a migration script to update all of the existing data that was incorrectly saved.

It only impacted one property and for applications that submitted in non-english so this script targets just those applications

How Can This Be Tested/Reviewed?

In order to test this you'll need to have a copy of the production database since it is reliant on the listing id and the specific preferences that are on that listing

Checklist:

• My code follows the style guidelines of this project
• I have added QA notes to the issue with applicable URLs
• I have performed a self-review of my own code
• I have reviewed the changes in a desktop view
• I have reviewed the changes in a mobile view
• I have commented my code, particularly in hard-to-understand areas
• [] I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have assigned reviewers
• I have run yarn generate:client and/or created a migration if I made backend changes that require them
• My commit message(s) is/are polished, and any breaking changes are indicated in the message and are well-described
• Commits made across packages purposefully have the same commit message/version change, else are separated into different commits

Reviewer Notes:

Steps to review a PR:

• Read and understand the issue, and 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
• Also review the acceptance criteria on the Netlify deploy preview (noting that these do not yet include any backend changes made in the PR)
• Either explicitly ask a clarifying question, request changes, or approve the PR if there are small remaining changes but the PR is otherwise good to go

On Merge:

If you have one commit and message, squash. If you need each message to be applied, rebase and merge.

[netlify]

✅ Deploy Preview for housing-sanjoseca-gov ready!

Name	Link
🔨 Latest commit	2cc244d
🔍 Latest deploy log	https://app.netlify.com/sites/housing-sanjoseca-gov/deploys/65c69ed993e7ad00084918db
😎 Deploy Preview	https://deploy-preview-662--housing-sanjoseca-gov.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]

LGTM