update legal filings job - clean up errors

Two things that should be done:
- when encountering any bn failure it should skip it and process the other bns during its batch update (right now 1 failure causes all to fail)
- in dev/test/prod we have several outdated COOP filings that are trying to update on repeat causing many errors in our logs:
- we should be skipping irrelevant data issue examples in dev/test (discuss potential solutions)
- evaluate the prod errors and resolve them

Start by locating the legal filings job and reviewing how batch updates handle BN failures. Inspect the dev, test, and prod errors for outdated COOP filings, then verify that one failed BN no longer stops the batch, irrelevant filings are skipped in dev/test, and the identified production errors are resolved.

Written by the indexing model from the issue text.