Add option to specify conda env for LSF job

[pcm32]

Currently to run an LSF job inside a conda environment different to the current environment (usually this package's), one needs to add some twisted direct invocation of activate and the env with complete paths:

export ENV_COMMAND=". $SOFTWARE/miniconda3/bin/activate $SOFTWARE/miniconda3/envs/my-env"

atlas-lsf \
  -c "$ENV_COMMAND && my-command"

it would be nice if instead we could do:

atlas-lsf \
  -v my-env \
  -c my-command

the script would need to resolve the conda base and then call from there activate and the my-env with their full paths as it is done on the env variable above. Maybe a nice first contribution from @irisdianauy ?

[pinin4fjords]

Just putting the Nextflow equivalent here for further illustration:

source $(conda info --json | awk '/conda_prefix/ { gsub(/"|,/, "", $2); print $2 }')/bin/activate /nfs/production/irene/ma/fg_atlas_sc/nextflow_scxa/envs/salmon-fec68f5d709540071be9f969ca06fcf9