Feature: Write build caches to S3

[ewilkins-csi]

Description

In #429 we started saving the Docker build cache during the build workflow. We discussed that the size of the Docker cache may end up causing issues and it has. Because it's ~9GB, the docker cache will often cause all other caches to be purged and, at least once, has failed to save seemingly due to its size. In addition, it takes about 9.75 mins to save the cache to GH caches. We should go ahead and implement the Runs-On S3 fast cache action to get around these issues.

DOD

• [x] The build workflow authenticates with AWS and writes caches to S3
• [x] The S3 bucket is configured to delete objects a day after their creation
  • We could instead use the AWS authentication to delete the caches during the build itself, but that requires more permissions on S3 and is less straight-forward to implement

Test Strategy/Script

1. View the latest build and verify the cache actions are from the runs-on/cache action
2. Confirm the caches saved to AWS are < 1 day old

[ewilkins-csi]

DoD/OTS with @csun-cpointe and @carter-cundiff

[csun-cpointe]

Test passed! Confirm the caches saved to AWS are < 1 day old

View the latest build and verify the cache actions are from the runs-on/cache action