Update `which` command in condaCloud.sh for robustness

[xiangtaoxu]

I also ran into some environmental path errors when activating CloudComPy310 conda environment on our HPC cluster (operating system is Rocky 9).

The reason is that which command does not skip functions/aliases by default, leading to empty values for CONDA_ENV_PATH.

Changing which python and which conda in condaCloud.sh to which --skip-alias --skip-functions python and which --skip-alias --skip-functions conda solve the problem