Conda is behaving strangely on CCB server because of conda install at /usr/condabin
after sourcing conda correctly, activating a new environment alters the path to no longer pick up correct conda or mamba from base env when in a different environment.
this is likely related to [https://github.com/conda/conda/issues/9392] and multiple conda installs - particuarly /usr/condabin is added to path and conda recognises this before your proper condainstall
Conda is behaving strangely on CCB server because of conda install at /usr/condabin