Reconciliation service for S3 / minio payload offload

[lmsurpre]

Is your feature request related to a problem? Please describe.
With payload-offloading, the call to store the payload is made before the RDBMS transaction commits. If the transaction is rolled back, an attempt is made to delete any payloads which were stored as part of the transaction. However, it is possible that the delete call could fail (a network partition, maybe) in which case resource records will exist in the offload store, but not the RDBMS.

Describe the solution you'd like
Make it work like the azure-blob one.

Should we have a single module / cli jar that handles both s3 / minio AND azure-blob? Or just copy the fhir-persistence-blob-app project to a new one named fhir-persistence-cos-app (or fhir-persistence-s3-app)?

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Acceptance Criteria

1. GIVEN [a precondition]
   AND [another precondition]
   WHEN [test step]
   AND [test step]
   THEN [verification step]
   AND [verification step]

Additional context
Just like #3143 but for s3 / minio