Refactor for libmamba v2 (WIP)

[jaimergp]

Description

Adds compatibility for libmamba v2, which enables a few refactors (see below). Supersedes #414.

• Will close conda with libmamba solver does not work in offline mode conda#13953

Progress:

• Refactor index helpers
• Refactor repoquery
• Refactor solver
• Refactor conflict reports
• Pass all tests
• Polish and clean up

Checklist - did you ...

• Add a file to the news directory (using the template) for the next release's release notes?
• Add / update necessary tests?
• Add / update outdated documentation?

Summary of changes

• Deprecate CONDA_LIBMAMBA_SOLVER_NO_CHANNELS_FROM_INSTALLED. No longer needed with v2. Closes CLS injects channels from installed packages #411
• Added typing for all methods and functions
• Added time_recorder decorator for metadata collection and solving loop
• Removed state.BaseIndexHelper. We just have our index.IndexHelper now
• The libmamba v1 pool (collection of repos, where a repo represents a loaded repodata.json) is now a database of RepoInfo objects.
• Do use current_repodata.json if explicitly set in CLI
• Move to Ruff for pre-commit linting & formatting
• Logging from libsolv has a HUGE overhead now because it goes from C to C++ to Python to logging to stdout instead of C -> stdout. To enable libsolv verbosity, an extra environment variable CONDA_LIBMAMBA_SOLVER_DEBUG_LIBSOLV is required.
• allow_uninstall was previously set to false (only true for conda remove), and we set it up for individual solver jobs involving updates or conflicts. With v2, we have individual control over what to "Keep" instead of drop. This required marking important updates as keepers instead. Otherwise they would be uninstalled.
• Other changes in the test suite discussed in Amend test suite for compatibility with libmamba v2 conda#13784

[jaimergp]

pre-commit.ci autofix

[jaimergp]

We were debating whether to also add libmamba v1 compatibility in this PR, which would include copying the current code in main to a conda_libmamba_solver.v1 namespace and dispatch automatically from the plugin depending on the detected libmambapy version at runtime.

Sylvain also mentions that there's no need as long as conda allows old conda-libmamba-versions. Worst case, if we needed to release a bugfix, we could do 24.7.x patches til necessary.

That latter option seems simpler than the .v1 namespace, if you ask me, but I'll let this here in case someone has thoughts.

[jaimergp]

Funny, now that we patched conda-libmamba-solver to prevent libmambapy 2, we can't install it in CI :D This is going to require some hacks or rewriting parts of the CI...

Edit: Built a special conda-libmamba-solver build (off main) but with the libmambapy<2 constraints removed and added it to a label in my channel for now. Thanks to strict priority, this will be chosen before conda-forge's and then a solution will be found.

[jaimergp]

Since the canary workflow has a token issue for the uploads, I built it locally.

• Direct URL: https://anaconda.org/jaimergp/conda-libmamba-solver/24.7.0.125_ga3d9a3d/download/noarch/conda-libmamba-solver-24.7.0.125_ga3d9a3d-py_0.tar.bz2
• Logs: log.txt.zip
• Command:

conda install -c jaimergp/label/conda-libmamba-solver_dev -c conda-forge/label/mamba_dev -c conda-forge conda-libmamba-solver

[conda-bot]

Review build status

The workflow for building and uploading a canary release for conda-libmamba-solver with the label conda-libmamba-solver-pr-457 in channel conda-canary was started by @jaimergp!

Once it's done, use this command to try it out in a new conda environment:

conda install -c conda-canary/label/conda-libmamba-solver-pr-457 conda-libmamba-solver

• build 10004917133 succeeded on Linux (X64)