Pass --quiet flag in build-in-devcontainer workflow

[TomAugspurger]

This passes the --quiet flag to the environment creation command, to avoid noisy output from progress bars like https://github.com/rapidsai/cudf/actions/runs/16429104215/job/46426604875?pr=19411#step:9:2240.

[TomAugspurger]

Do we want this? If so, is there a way to test it before merging?

[gforsyth]

Hey @TomAugspurger -- I remember something about us trying to use the --quiet flag and it doing something weird, but I can't remember the details. I can ping the rest of the build team and see if anyone else can recall.

Overall, yes, I think getting rid of the weird unrolled progress bar would be great for our logs. In re: testing, someone on build engineering can push your commit to a non-fork branch of shared-workflows, then in a given repo (usually rmm because it builds quickly) you can change the targeted branch in the downstream workflow yaml files.

[bdice]

Here are the historical issues we had with enabling --quiet:
rapidsai/ci-imgs#220
rapidsai/ci-imgs#228

[trxcllnt]

We were passing -q until recently, so I think this should be fine. Could also just set the environment variable CONDA_ENV_CREATE_QUIET=1