Add CEP for conda-lock.yml lockfiles

[jaimergp]

Checklist for submitter

• I am submitting a new CEP: conda-lock.yml lockfiles.
  • I am using the CEP template by creating a copy cep-0000.md named cep-XXXX.md in the root level.
• I am submitting modifications to CEP XX.
• Something else: (add your description here).

Checklist for CEP approvals

• The vote period has ended and the vote has passed the necessary quorum and approval thresholds.
• A new CEP number has been minted. Usually, this is ${greatest-number-in-main} + 1.
• The cep-XXXX.md file has been renamed accordingly.
• The # CEP XXXX - header has been edited accordingly.
• The CEP status in the table has been changed to approved.
• The last modification date in the table has been updated accordingly.
• The table in the README has been updated with the new CEP entry.
• The pre-commit checks are passing.

[jaimergp]

cc @maresb, lmk what you think!

[maresb]

I've taken an initial quick pass and this looks pretty good. Ping @basnijholt.

I think it may be helpful to provide the following additional context:

There's a "unique" constraint on the package list with key (name, manager, platform, category).

Currently known producers:

• conda-lock lock, https://github.com/basnijholt/pixi-to-conda-lock

Currently known consumers:

• conda-lock install, micromamba env create

[maresb]

We should update the ref here once we cut the next release, since we change version from ClassVar to Literal[1].

[jaimergp]

Thanks for the prompt review!

There's a "unique" constraint on the package list with key (name, manager, platform, category).

Added in ee2dff0.

Actually md5 and sha256 are technically optional.

Reworded in a6d58bc.

Currently known producers:

Thanks! Added in 1202623. Note that conda-lockfiles is also a thing now.

[maresb]

This is awesome! I've wished for this for a long time, and it's great to finally have it.

All my feedback (apart from the future version bump in the conda-lock link) has been incorporated. I made another pass and didn't notice any further issues.

Thanks again @jaimergp!!!