Add GitHub Action workflow to update Micromamba

[jakirkham]

To aid in keeping Micromamba up-to-date in images, it may help to have a GitHub Action that checks for an existing release and if it finds one updates the version...

docker-images/scripts/run_commands

Line 9 in 7023391

export micromamba_version="1.5.10-0"

...as well as associated checksums...

docker-images/scripts/run_commands

Line 15 in 7023391

export micromamba_chksum="80057e007579d482a39dc283dd3e725503e34da7e7c51844957164511cdb917b"

docker-images/scripts/run_commands

Line 19 in 7023391

export micromamba_chksum="5528e92b12f7389a8d23a409a476e871f4f889a17e381924cf74459f14627ddd"

docker-images/scripts/run_commands

Line 23 in 7023391

export micromamba_chksum="7803a2aa51a5f0a58f3d2ef0f07724edb67f31f61b3e44ae9b8d6c9f009f7996"

[jakirkham]

Another option may be to install our own conda-forge package of micromamba

That way updating of the package would happen in the feedstock. Regular builds of the Docker images would pick up any new versions when they are available

[jaimergp]

Note micromamba 2.x has a bug with ssl certificates not being found. Didn't check if the latest bugfix releases addresed it though. I'll link to the issue once I get to my desk.

Thanks!

[jaimergp]

This is the issue: mamba-org/mamba#3570.

[jaimergp]

Another option may be to install our own conda-forge package of micromamba

I remember @isuruf mentioned there was a bug with conda-installing micromamba some time ago (something related with PREFIX replacement?), not sure if that ever got addressed or even if it's documented.