Filer - integrate with auth listener for IA & Registration filings

The filer previously interacted with auth directly via auth api calls. This code has been commented out in the filer in the meantime.

Moving forward, this communication with the auth api will take place via the auth listener.

To make this happen, the filer will need to be updated to send a queue message to the auth listener where appropriate.

**TODOs**
- [ ] Update code to send a queue message to auth topic where api calls were made previously for IA & registration filing. Take a look at auth listener code in queue services to figure out the queue message format it expects
- [ ] Remove commented out auth calls once replaced
- [ ] Add required config as required to `config.py` and `/devops/vaults.gcp.env`
- [ ] Remove old config as required from `config.py` and `/devops/vaults.gcp.env`
- [ ] Update corresponding tests as appropriate. There may be a need to mock some of the queue pieces to ensure test continue working.

Start by comparing the commented auth API call sites in the filer with the auth listener implementation in queue services, including its expected message format. Then review config.py, /devops/vaults.gcp.env, and the corresponding tests; done means IA and registration filing paths use the listener, obsolete calls and config are removed, and tests cover the queue interaction.

Written by the indexing model from the issue text.