update conda-lock version after updates

[JessicaS11]

The most recent (v1.1.3) version of conda-lock includes a switch (that happened in v1.1.0 with PR#89) from relative to absolute paths. As a result, whenever someone new updates the conda lock files, their local dir path is added to the lockfile source list (and other users get a warning for every path listed that's not on their local machine). It looks like a fix is in the works, so I reverted to v1.0.5 until this update is implemented. @weiji14, please let me know if this will be an issue for anything you added and we can deal with the warnings until the update lets us specify relative paths.

[weiji14]

Thanks Jessica, I was going to switch to a generic /home/jovyan path (see 57e6b3fcf9bd1f91b8bd31d31150a3d10bd9d917), but even better if conda-lock fixes it upstream! Feel free to mess around with the lockfiles if needed.

[JessicaS11]

Conda-lock has officially closed this issue as fixed (not sure if it's yet released): conda/conda-lock#229

[weiji14]

Conda-lock 2.0.0 was released which also included conda/conda-lock#328 that handles the relative paths a bit better still. I'll update the GitHub Actions workflow to use conda-lock 2.0.0 in #14.

[weiji14]

This issue is actually referring to the lockfile on https://github.com/CryoInTheCloud/CryoCloudWebsite/tree/main/conda (where the build stuff used to happen). We've been using conda-lock>=2.0.0 for a while now on https://github.com/CryoInTheCloud/hub-image (conda-lock=2.3.0 as of #91), so I'll close down this issue. Feel free to reopen if needed.