ISIS 10.1.0_RC1 cannot function without ISIS conda env active

**ISIS version(s) affected**: 10.1.0_RC1, MacOS 26.5.2

**Description**
With ISIS 10.0.0 (and every single prior version), I can start with my `base` conda enviroment (or any other non-ISIS environment) active, and do the following:
```
export ISISDATA=/scratch0/ISIS_DATA/
export ISISROOT=/Users/rwagner/miniforge3/envs/isis10.0.0
export PATH="$PATH:$ISISROOT/bin"
maptemplate
```
and maptemplate (or any other ISIS command) will run normally. With 10.1.0_RC1, the same sequence (with the 10.1.0_RC1 environment instead of 10.0.0), I instead get the following error:
```
$ maptemplate
libc++abi: terminating due to uncaught exception of type std::runtime_error: Alias map JSON file [/Users/rwagner/miniforge3/etc/SpiceQL/aliasMap.json] not found.
Abort trap: 6
```

If I instead `conda activate isis10.1.0_RC1` and run maptemplate, it works fine, but then I'm required to use the isis conda environment in order to use ISIS programs, which is... very limiting.

To be clear, this isn't limited to maptemplate, it affects almost every single ISIS command, maptemplate is just my go-to test.

**Possible Solution**

My guess is that somewhere in the SpiceQL stuff you're using CONDA_PREFIX to find python3, rather than ISISROOT or some sort of self-relative path, since adding `CONDA_PREFIX=/Users/rwagner/miniforge3/envs/isis_10.1_RC` gets maptemplate launching correctly. (Note also that it's not a $PATH order issue, putting ISISROOT/bin first doesn't change anything, although it does defeat the point of having another conda env active by putting the wrong python3 first.)

Reproduce the failure by exporting ISISDATA, ISISROOT, and PATH without activating the ISIS environment, then compare it with an activated environment. Start by tracing how the SpiceQL alias map path is resolved; done means maptemplate and other ISIS commands run successfully from a non-ISIS conda environment.

Written by the indexing model from the issue text.