Filer - Update special resolution filing processor to work with alternate name changes

Update filing processors such that we are work with alternate_name entries if required. With the new data model, SPs will need to use alternate_name similar to the way we use a legal_entity record.

If the filing processor only works with legal entity records, it may be the case that no major updates need to be made to work with alternate_names.

For each filing processor, do the following:
- [ ] Do work in legal name branch
- [ ] Update to work with alternate names and legal entities
- [ ] There may be some other misc updates required to get processor working. Update as appropriate.
- [ ] Update LegalEntity, AlternateName and Filings model manually in common models to match with legal api models as required. If #19451 has been completed, this may not be required
- [ ] Update worker.py as required
- [ ] Update to ensure that everything is persisted and retrieved correctly according to new data model
- [ ] ignore alias logic. work will be done in another ticket
- [ ] Update tests relevant to this filing processor

Start with the special resolution filing processor and worker.py, then compare LegalEntity, AlternateName and Filings in the common models with the legal API models. Run the relevant filing-processor tests first; done means legal-name and alternate-name cases persist and retrieve correctly, with alias logic excluded.

Written by the indexing model from the issue text.