fix: update warn user of deletion email (bloom-housing#6394)

[ludtkemorgan]

This PR addresses #1536

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

Description

Pulls the commit from core related to user deletion email content update

How Can This Be Tested/Reviewed?

Verify the email translations are updated

In order to test that the migration file properly works manual validation is required.

1. Before pulling down these changes seed the database
2. Pull down the changes and run yarn db:migration:run
3. Verify that the database has the new fields and updated language for the accountRemoval field in the translations table

Verify the email looks correct

1. Seed the database
2. Create a public user with your email
3. In the database update the last_login_at and password_updated_at to be way in the past
4. Set the USER_DELETION_WARN_CRON_STRING value in the .env file to run soon (ideally the next few minutes)
5. Set the USERS_DAYS_TILL_EXPIRY value in .env file to be a small number (e.g 1)
6. Wait for the cron job to run and verify the received email looks correct

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

[mcgarrye]

lgtm