[llvm] workflows: Rewrite build-ci-container to work on larger runners (PR #117353)

[Tom Stellard via llvm-commits]

tstellar wrote:

> > The Foundation is providing a small budget for testing them out. We're using 'Depot Managed' which means the instances are deployed in the Foundation's AWS account rather than using the machines from Depot's pool.
> 
> Ah, okay. I didn't realize that had taken place. Thanks for the additional context.
> 
> > Are these ready to use now? I don't have a preference for which runners to use.
> 
> Theoretically, yes, they are ready to use and should just work. We can only run one job at a time currently though because we don't have enough quota in the region where the cluster is deployed, but that should be enough for testing. @lnihlen is working on getting additional quota. I think it would probably make more sense to use the Google hosted runners given it doesn't require any budget from the foundation, and lets us consolidate on a single system.
> 

OK, do you think I should update this PR to use those runners instead or wait a few weeks?

> I think our runners will also be more powerful too (configured to be 56 vCPUs), but depends upon how the depot runners are configured.

Depot runners are up-to 64 CPUs.  The number of CPUs is part of the runs-on label so you can choose the right size machine that fits the job.

https://github.com/llvm/llvm-project/pull/117353