Finish obfuscating C&E fields for when we copy Prod -> Test

### Devs are going to obfuscate as they go through the ETL, so this ticket is to capture all C&E fields, not just the those with data being ETL'd from NRIS

As the product owner, I want to see C&E data obfuscated in Test where appropriate, after a fresh pull from Production.

**Fields for obfuscation:**

alcs.compliance_and_enforcement
- [ ] alleged_contravention_narrative
- [ ] intake_notes

alcs.compliance_and_enforcement_property
- [ ] alc_history

alcs.compliance_and_enforcement_submitter

- [ ] name
- [ ] email
- [ ] telephone_number
- [ ] affiliation
- [ ] additional_contact_information

alcs.compliance_and_enforcement_responsible_party

- [ ] individual_name
- [ ] individual_mailing_address
- [ ] individual_telephone
- [ ] individual_email
- [ ] individual_note
- [ ] ~~organization_name~~ -> do not obfuscate
- [ ] organization_mailing_address
- [ ] organization_telephone
- [ ] organization_email
- [ ] organization_note

alcs.compliance_and_enforcement_responsible_party_director

- [ ] director_name
- [ ] director_mailing_address
- [ ] director_telephone
- [ ] director_email

alcs.compliance_and_enforcement_document

- [ ] the document itself

alcs.compliance_and_enforcement_chronology_entry
- [ ] description

Add notice, order, appeal, etc once the fields are in the ALCS db

Start by tracing the fresh Production-to-Test ETL and the ALCS database handling it uses; the payload names no files or tests. Check each listed C&E field and the document for obfuscation, preserve organization_name, and extend coverage to notice, order, appeal, and other records once those fields are in the database.

Written by the indexing model from the issue text.