Problem Description:

When a user deprecates a collection, it gets deprecated in the repository the user is currently operating in https://github.com/pulp/pulp_ansible/blob/main/pulp_ansible/app/galaxy/v3/views.py#L332. That deprecation status does not propagate into other repos where the content is present. For example if you deprecate in the `published` repo and that content also exists in `123456-synclist` the collection will not show as deprecated in `123456-synclist`

There also exists a related but independent pulp-ansible correctness migration issue which causes a migration error with a particular set of data: https://github.com/pulp/pulp_ansible/issues/791

Proposed Remediation:

1. Turn off deprecation in the UI so no new collections are deprecated until solution is in place
2. Delete the 3 collections

Proposed Solution:

1. Fix the copy/promotion implementation on galaxy_ng to propagate the deprecation status/content to the new repo when a collection version is copied.
2. Fix the synclist curate impementation by either:
   1. Fix in code as above
   2. Move away from using synclist functionality, per AAH-534