fix: improve listing deletion process

[mcgarrye]

This PR addresses #(insert-number-here)

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

Description

With the implementation of the ExternalListingService, it was found that a number of associated records with a listing record do not cascade on delete. Unfortunately, most of these would require a serious refactor with dedicated time and lift. This is covered in this backlog ticket.

This PR adds the cascade onDelete for unitGroups and unitGroupAmiLevels.
It also adds a manual delete of the address associated as the ListingBuildingAddress for a listing in the ExternalListingService.

How Can This Be Tested/Reviewed?

Through the API, call GET /externalListings

Using the data returned in the above GET response, call PUT /externalListings/ingest with the following payload
{ externalURL: 'http://localhost:3100', jurisdictionId: '{jurisdictionId}', targetName: '{jurisdictionName}', }
Should duplicate all active listings in the target jurisdiction with external fields filled out. Verify in the database.
Choose a listing to edit and store the listing id and associated buildingAddressId of the external copy
Edit the internal listing (or change contentUpdatedAt in the db)
Confirm in the db that the listing was delete AND the address with id = buildingAddressId

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 bloom-angelopolis canceled.

Name	Link
🔨 Latest commit	b8d977f
🔍 Latest deploy log	https://app.netlify.com/projects/bloom-angelopolis/deploys/6a5515853067dd00084b4216

[netlify]

✅ Deploy Preview for partners-bloom-dev ready!

Name	Link
🔨 Latest commit	b8d977f
🔍 Latest deploy log	https://app.netlify.com/projects/partners-bloom-dev/deploys/6a551585ca8b840008962a34
😎 Deploy Preview	https://deploy-preview-6491--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 project configuration.

[netlify]

✅ Deploy Preview for bloom-exygy-dev ready!

Name	Link
🔨 Latest commit	b8d977f
🔍 Latest deploy log	https://app.netlify.com/projects/bloom-exygy-dev/deploys/6a55158459144e00081ed66a
😎 Deploy Preview	https://deploy-preview-6491--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 project configuration.

[ludtkemorgan]

functionally looks good! I just recommend you update the PR title to be more descriptive of what this PR does since the cascade delete is just small part.