util/s3: enable more credential providers

[algolucky]

this will not be live until update.sh is updated to use the version this updater is released with, e.g.

go-algorand/cmd/updater/update.sh

Line 4 in 026f0aa

UPDATER_MIN_VERSION="3.12.2"

Summary

• updates the s3Helper to allow more credential providers. now AWS_ environment variables, config files, and EC2 metadata are supported credential providers when using tools like updater and goal logging send.
• removes error if AWS_ environment variables are not set
• removes the ability to configure credentials with a s3.json file
• forces use of Anonymous credentials when communicating with algorand-releases
• if no credentials are found, it uses Anonymous credentials

Test Plan

• ci
• internal performance testing

[codecov]

Codecov Report

Merging #4929 (026f0aa) into master (3fbe53c) will decrease coverage by 0.00%.
The diff coverage is 20.00%.

❗ Current head 026f0aa differs from pull request most recent head 3c49eed. Consider uploading reports for the commit 3c49eed to get more accurate results

@@            Coverage Diff             @@
##           master    #4929      +/-   ##
==========================================
- Coverage   53.51%   53.50%   -0.01%     
==========================================
  Files         432      432              
  Lines       53615    53624       +9     
==========================================
  Hits        28691    28691              
- Misses      22695    22702       +7     
- Partials     2229     2231       +2     

Impacted Files	Coverage Δ
logging/cyclicWriter.go	46.46% <0.00%> (-3.00%)	⬇️
logging/telemetryhook.go	50.70% <50.00%> (+0.34%)	⬆️
crypto/merkletrie/trie.go	66.42% <0.00%> (-2.19%)	⬇️
crypto/merkletrie/node.go	91.62% <0.00%> (-1.87%)	⬇️
catchup/peerSelector.go	98.95% <0.00%> (-1.05%)	⬇️
catchup/service.go	69.32% <0.00%> (-0.49%)	⬇️
ledger/acctupdates.go	68.99% <0.00%> (-0.25%)	⬇️
network/wsPeer.go	69.45% <0.00%> (+0.47%)	⬆️
ledger/testing/randomAccounts.go	56.88% <0.00%> (+1.22%)	⬆️
ledger/blockqueue.go	88.50% <0.00%> (+2.87%)	⬆️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[algobarb]

It looks much more clean now. What is the benefit of changing it to "only uses Anonymous credentials when communicating with algorand-releases" if bucket == s3DefaultReleaseBucket?

[algolucky]

@algobarb for this specific scenario:

I am in my account, on an EC2 with an IAM role. If that IAM role does not have access to S3, then updater will return a 403.

This is just a shortcut so that whenever updater is dealing with algorand-releases we use anonymous credentials (or no credentials). when there are no credentials passed, GET on algorand-releases should work.

[algobarb]

LGTM