Update response code for container registry api bulk delete

What does this MR do?

This merge updates the container registry API bulk delete endpoint to return 400 if the same request is made multiple times within 1 hour. The worker that the endpoint creates was checking the lease, but since the lease status is required in order to send the proper response, the code to check the lease was moved from the worker to a new service that checks the lease and only runs the worker if there is not a current lease. This allows the service to inform the API endpoint which response to return (202 or 400).

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation created/updated or follow-up review issue created
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Performance and testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers

Closes #62183 (closed)