Testing OpenSSL 3.5.2 vs OpenSSL 3.5.3+ stability issues

[rockhowse]

We have seen some instability when allowing the conda environment when using OpenSSL 3.5.3+

• https://github.com/rapidsai/ci-imgs/actions/runs/18845890788/job/53769945953

Due to these issues, pinned this repo to ensure we are using OpenSSL 3.5.2 in our conda environments:

• Pin openssl<3.5.3 to fix mamba hangs in CI #313

This PR is being used to dump some more detailed information about how mamba connectivity is being done at the lowest level to ideally help us identify issues with the newer version of OpenSSL 3.5.3+

[rockhowse]

@msarahan this is not intended to be reviewed... need an active PR to trigger the builds fail with OpenSSL 3.5.3+. I am using it to get some verbose connectivity logging with OpenSS 3.5.2 (doesn't exhibit the issue) and OpenSSL 3.5.4 (the version that was causing issues in PRs/nightlies)

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[rockhowse]

/ok to test

[copy-pr-bot]

/ok to test

@rockhowse, there was an error processing your request: E1

See the following link for more information: https://docs.gha-runners.nvidia.com/cpr/e/1/

[rockhowse]

/ok to test e31b06d

[rockhowse]

/ok to test 955515d

[gforsyth]

Great work tracking this down @rockhowse -- I'd say let's go ahead and commit your suggestions to remove the (commented out) pins and extra workaround comments, and then merge this in.

[rockhowse]

resolves https://github.com/rapidsai/build-infra/issues/305