Add retries to HTTP timeouts in Meadow.Search.HTTP and Meadow.Utils.AWS

[mbklein]

Summary

Add HTTP retries to AWS and OpenSearch clients

Specific Changes in this PR

• Add retry functionality to Meadow.Search.HTTP.request/5
• Add retry functionality to Meadow.Utils.AWS.request/2

Version bump required by the PR

See Semantic Versioning 2.0.0 for help discerning which is required.

• Patch
• Minor
• Major

Steps to Test

This is a tricky one to test. A largish ingest sheet should go through successfully (all the way through to indexing), but there's no way to guarantee a timeout will happen so there's no way to guarantee that you'll see it recover from one. Best choice is to see that it doesn't break anything, and watch for further errors in production.

🚀 Deployment Notes

Note - if you check any of these boxes go to the (always open) main <- staging PR and add detailed notes and instructions to help out others who may end up deploying your changes to production

• Backward compatible API changes
  • Database Schema changes
  • GraphQL API
  • Elasticsearch API
  • Ingest Sheet
  • CSV metadata export/update API
  • Shared Links export API
• Backwards-incompatible API changes
  • Database Schema changes
  • GraphQL API
  • Elasticsearch API
  • Ingest Sheet
  • CSV metadata export/update API
  • Shared Links export API
• Requires data migration
• Requires database triggers disabled during deployment/migration
• Requires reindex
• Terraform changes
  • Adds/requires new or changed Terraform variables
• Pipeline configuration changes (requires mix meadow.pipeline.setup run)
• Requires new variable added to miscellany
• Specific deployment synchronization instructions with other apps/API's
• Other specific instructions/tasks

Tested/Verified

• End users/stakeholders