fix(dev/release): call conda init before conda activate

[zeroshade]

Ran into an issue when running verify-release-candidate.sh using USE_CONDA=1. Got an error specifying that we need to call conda init before conda activate base. After adding that line the verification was able to continue.

[ianmcook]

After adding this line to the verification script, I'm still seeing this in the output (but it doesn't cause any failure):

=====================================
Build, install and test C++ libraries
=====================================
└ Ensuring that Go is installed...
└ Configuring Conda environment...

CondaError: Run 'conda init' before 'conda deactivate'

└ Ensuring that Conda is installed...

[lidavidm]

I'm not sure we want this, doesn't conda init write to the user's bash_profile and such?

[zeroshade]

hmm, we could add the --no-user argument so that it doesn't initialize for the current user?

[amoeba]

Does that work? I just tested it and it doesn't do anything:

$ env | grep CONDA

$ conda init --no-user
-- >8 -- 
No action taken.

$ env | grep CONDA

$ conda activate adbc

CondaError: Run 'conda init' before 'conda activate'

Most users will already have run conda init so this would be adding a workaround to the verification script for users who install but don't fully set conda up?