Fix CI Multiple aliased keys in file /Users/runner/.condarc

[jacobtomlinson]

Closes #9135

There seems to be a conflict between auto activating the CI environment, and disabling the auto activation of the base environment. I'm a little confused as to why this happened because we pin the conda action to a specific version.

Trying out this quick fix to remove the disable base activation setting given that we specify which environment should be activated anyway.

[jacobtomlinson]

Digging a little further this PR suggests that the config setting has been renamed, so maybe we should update the name instead of removing it. I'm not sure how much it matters though.

I'll wait for CI here and if it's all happy then I'll probably just merge it as is.

[fjetter]

I believe the activation is handled by the action. looks like some builds already passed, so it should be fine

[github-actions]

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

    27 files  +    27      27 suites  +27   9h 52m 56s ⏱️ + 9h 52m 56s
 4 112 tests + 4 112   4 006 ✅ + 4 006    104 💤 +  104  2 ❌ +2 
51 516 runs  +51 516  49 330 ✅ +49 330  2 184 💤 +2 184  2 ❌ +2 

For more details on these failures, see this check.

Results for commit 8225468. ± Comparison against base commit 1ee4756.

[jacobtomlinson]

That's a lot less failures, just flaky stuff. Merging.