fix: make empty bucket use queue to remove underlying objects asynchronously

[itslenny]

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

When a bucket is emptied it sends DeleteObjectsCommand to S3 in a tight loop resulting in rate limit errors and ultimately orphan objects.

What is the new behavior?

Use the queue to delete objects from the underlying object store asynchronously

Additional context

This adds ObjectDeleteAllBeforeEvent which recursively removes all objects before a specified time in batches using storage.backend.deleteObjects(...) within a transaction so the database objects will be rolled back if the S3 operation fails.

Each job run removes as many batches as it can in 10 seconds and then re-queues if there are remaining objects to delete.

[coveralls]

Pull Request Test Coverage Report for Build 16450960387

Details

• 174 of 221 (78.73%) changed or added relevant lines in 9 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage increased (+0.02%) to 76.953%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/storage/database/knex.ts	32	33	96.97%
src/storage/events/workers.ts	2	3	66.67%
src/storage/storage.ts	23	25	92.0%
src/internal/errors/codes.ts	2	7	28.57%
src/storage/events/objects/object-admin-delete-all-before.ts	103	141	73.05%

Files with Coverage Reduction	New Missed Lines	%
src/internal/errors/codes.ts	1	72.02%

Totals
Change from base Build 16426721998:	0.02%
Covered Lines:	20551
Relevant Lines:	26475

---

💛 - Coveralls