ci: use project bucket for assets COMPASS-10105

[mabaasit]

We are moving away from storing artifacts in mciuploads to project specific S3 buckets. DEVPROD-25311 documents how to create these buckets.

Description

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• If this change updates the UI, screenshots/videos are added and a design review is requested
• If this change could impact the load on the MongoDB cluster, please describe the expected and worst case impact
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)

[addaleax]

Do these needs to be -private instead of -public? With -private, we can't pass URLs to these builds to people anymore (esp. customers outside of the org), and it makes bulk downloads quite a bit more annoying (which I've had to do for SSDLC artifact compilation from time to time)

[mabaasit]

I am checking this with the team if these can be public.

[mabaasit]

So, backstage created s3 buckets with public access disabled and that's why I was not able to upload assets with public access which forced me to use private. DEVPROD will change this and I'll revert this bit.