Add support for direct upload to r2 buckets

[pwgardipee]

What does this PR do?

Allows files to be directly uploaded to R2 buckets when the output_dir points to a lightning_storage folder.

https://www.loom.com/share/8ef98a2adc0c4f7b86543bab9679882d?sid=387f8cbd-48a2-417e-8058-2346d14736d3

Questions for @tchaton and/or @bhimrazy:

1. We need the data_connection_id in order to fetch the temporary credentials for the r2 bucket. I wasn't able to find a graceful way of threading that through from the output_dir to the get_bucket_and_path function without adding a ton of code, so I just setting an env var and reading from that. This feels very hacky so let me know if you have any recommendations.
2. It seems like we should have get_r2_bucket_credentials call an SDK method instead of making a direct API call. I can do this in a followup PR unless you think it's necessary now.

Fixes # (issue).

PR review

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in GitHub issues there's a high chance it will not be merged.

Did you have fun?

Make sure you had fun coding 🙃

[tchaton]

Good start. I would be good to add some tests.

[codecov]

Codecov Report

❌ Patch coverage is 70.07299% with 41 lines in your changes missing coverage. Please review.
✅ Project coverage is 84%. Comparing base (0b19ba6) to head (3336fe1).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@         Coverage Diff          @@
##           main   #705    +/-   ##
====================================
  Coverage    84%    84%            
====================================
  Files        52     52            
  Lines      7078   7200   +122     
====================================
+ Hits       5957   6076   +119     
- Misses     1121   1124     +3     

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[gitguardian]

️✅ There are no secrets present in this pull request anymore.

If these secrets were true positive and are still valid, we highly recommend you to revoke them.
While these secrets were previously flagged, we no longer have a reference to the
specific commits where they were detected. Once a secret has been leaked into a git
repository, you should consider it compromised, even if it was deleted immediately.
Find here more information about risks.

---

^{_{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}}

[robTheBuildr]

Found some testing code that needs to be removed.
Also need to clean up the "magic numbers" scattered in code

And probably base class for the Filesystem would be best

[tchaton]

Looks great ! Could you add some benchmarks in a follow up.