Description of problem:

Tekton Results database incorrectly shows Log record(s) as successfuly stored in S3 

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

 # TBD - only witnessed in some Konflux log records

• With Tekton Results setup with the logging plugin enabled and configured for S3
• Logs generally work as expected

Actual results:

• Some logs are not able to be fetched:
  • their database record says the log was successfully saved in S3
  • The S3 object referenced in the database does not exist

Expected results:

• The logs should be stored, and any which aren't stored shouldn't be in the database marked as stored

Reproducibility (Always/Intermittent/Only Once):

Very intermittant

Acceptance criteria: 

• All logs which the database claims are stored correctly exist in S3
• Any failure to store logs in S3 should update their database record accordingly and emit a useful log regarding the failure mode
• No logs should fail to be stored in S3 unless due to network issues, credential issues, other issues outside of the scope of Tekton Results, or acts of God.