Add ability to create environment from lockfile

[nkaretnikov]

This is a companion PR for conda-incubator/conda-store#772.

Description

This pull request: adds a new dropdown in the YAML window, which allows creating an env from a lockfile.

The supported lockfile type is https://conda.github.io/conda-lock/output/#unified-lockfile, which is also generated by conda-store as the lockfile build artifact.

Pull request checklist

• Did you test this change locally?
• Did you update the documentation (if required)?
• Did you add/update relevant tests for this change (if required)?

Additional information

Where to get a lockfile for testing:

• create a standard conda-store environment
• copy the generated lockfile from the build artifacts
• create an env with this lockfile by selecting the lockfile specification type and pasting the copied lockfile.

Manual tests:

• can create an environment using YAML -> lockfile specification type, deps and channels are updated on the GUI page on save
• can edit lockfile environment, same
• can edit a standard env and use lockfile type for the new revision
• can edit a lockfile env and use specification type for the new revision
• expected to not work: GUI is not updated without saving the env
• expected to not work: lockfile is created from a GUI alone (not enough information in the GUI to create a lockfile entry)
• expected to not work: no data is migrated when switching between specification types without saving

Future work:

• After this is merged, docs should be added to the conda-store repo describing the lockfile specification type. The supported lockfile type is https://conda.github.io/conda-lock/output/#unified-lockfile
• I had no time to create auto tests, some of the manual tests could be converted to auto tests.

[nkaretnikov]

I don't want to rely on any particular format here since it might change upstream.

[nkaretnikov]

This and similar code for deps is what populates GUI channels and dependencies lists on env save.

[nkaretnikov]

This is just to hint to the user which lockfile format is expected. Similar idea to formatCode above.

[nkaretnikov]

This file is the same idea as src/features/environmentVariables/environmentVariablesSlice.ts.

[nkaretnikov]

I only list conda packages and ignore pip because conda-store does the same for ordinary specs as well.

[nkaretnikov]

MenuItem values here match those we show in the admin interface (see the companion conda-store PR).

[nkaretnikov]

@gabalafou @peytondmurray PTAL. I'm currently on PTO, feel free to take over if this requires changes.

[gabalafou]

I pushed a few small changes.

I tested locally by copy-pasting lockfile from one environment to create another.

I feel that we should add a note to the UI that explains that GUI-Lockfile syncing has not been implemented. Otherwise I think an end user will find the app behavior confusing. I'll add that in a subsequent commit and then I think this should be good to go.

[gabalafou]

I just chatted with @trallard about this. I'm not sure we can move forward with this PR. This PR implements a UI that suggests to the end user that they can manually edit a lockfile, which can lead to very unintuitive behavior. For example (one we tested), if a user updates the version of a package in the lockfile, then clicks save, the version does not update because the backend (apparently) uses the url property and not the version string.

It seems that the correct implementation here should be a file upload button for the lockfile, not exposing it in the code editor.

[gabalafou]

Based on sprint planning meeting today, I'm closing this PR without merging because I will re-implement the UX for "create environment from a lockfile" as a file upload instead.