Bump lockfiles | Force user-installed conda during conda-lock

[abejgonzalez]

Testing the following theory:

conda-lock under the hood uses conda to solve some extra dependencies that are machine-specific in addition to the pre-computed lockfile dependencies. When it does this it uses a non-optimized version (i.e. without libmamba solver) of conda which is very slow for many dependencies. This PR forces conda-lock to use the conda that the user has installed (by doing which conda and passing that).

This also bumps the lockfiles, makes the default instructions include installing libmamba, and uses the most recent conda version in CI.

Related PRs / Issues:

Type of change:

• Bug fix
• New feature
• Other enhancement

Impact:

• RTL change
• Software change (RISC-V software)
• Build system change
• Other

Contributor Checklist:

• Did you set main as the base branch?
• Is this PR's title suitable for inclusion in the changelog and have you added a changelog:<topic> label?
• Did you state the type-of-change/impact?
• Did you delete any extraneous prints/debugging code?
• Did you mark the PR with a changelog: label?
• (If applicable) Did you update the conda .conda-lock.yml file if you updated the conda requirements file?
• (If applicable) Did you add documentation for the feature?
• (If applicable) Did you add a test demonstrating the PR?

• (If applicable) Did you mark the PR as Please Backport?

[abejgonzalez]

Tested on two machines:

Machine 1 (fresh conda install):

• With fix = ~1m30s to finish conda setup

Machine 2 (conda already installed and setup):

• With fix = 1m29s to finish conda setup
• Without fix = ~15m (14m39s)

So now build-setup.sh should go from O(30m) to O(15m) - really on our machines down to about ~10m

[jerryz123]

LGTM

[abejgonzalez]

@Mergifyio rebase main

[mergify]

rebase main

✅ Branch has been successfully rebased