[ci/coverage][2] upload coverage data to s3

[can-anyscale]

Why are these changes needed?

Add a --productionize flag to upload coverage data to s3 after computation

Checks

• [X] I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• [X] I've run scripts/format.sh to lint the changes in this PR.
• Testing Strategy
  • [X] Unit tests
  • [X] Release tests

python ci/test/ray_coverage.py //release:test_wheels --productionize
...
2023-05-03 16:15:27,655:INFO:botocore.credentials:Found credentials in environment variables.
2023-05-03 16:15:28,131:INFO:root:Successfully uploaded coverage data to s3 as continuous-release/ray-release-2023-05-03.cov

[stale[bot]]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

• If you'd like to keep this open, just leave any comment, and the stale label will be removed.

[can-anyscale]

save

[stale[bot]]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

• If you'd like to keep this open, just leave any comment, and the stale label will be removed.

[can-anyscale]

hi

[stale[bot]]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

• If you'd like to keep this open, just leave any comment, and the stale label will be removed.

[can-anyscale]

three

[stale[bot]]

Hi again! The issue will be closed because there has been no more activity in the 14 days since the last message.

Please feel free to reopen or open a new issue if you'd still like it to be addressed.

Again, you can always ask for help on our discussion forum or Ray's public slack channel.

Thanks again for opening the issue!