Clarify / improve the usage of conda-lock YAML spec file with `micromamba create`

[suimong]

Troubleshooting docs

• [X] My problem is not solved in the Troubleshooting docs

Anaconda default channels

• [X] I do NOT use the Anaconda default channels (pkgs/* etc.)

How did you install Mamba?

Micromamba

Search tried in issue tracker

conda-lock

Latest version of Mamba

• [X] My problem is not solved with the latest version

Tried in Conda?

Not applicable

Describe your issue

It seems that, to pass a conda-lock YAML spec file to micromamba create -f, one have to follow a certain naming pattern, i.e. "<whatever>-lock.<ya?ml>". I discovered this through trial and error (and a search through the codebase), when initially my conda-lock file is named conda-lock-setup.yml and micromamba seemed to treat it as conda yaml spec and complained about not having the "dependencies" section.

Currently the example in the documentation only shows usage with "conda-lock.yml", whereas the relevant test cases within the codebase seems to follow the naming pattern metioned earlier. It would be great to have the documentation, or better micromamba create --help, to be clearer and more explicit about the usage.

mamba info / micromamba info

libmamba version : 1.5.3
     micromamba version : 1.5.3
           curl version : libcurl/8.4.0 OpenSSL/3.0.12 zlib/1.3 brotli/1.1.0 zstd/1.5.5 libidn2/2.3.4 libssh2/1.11.0 nghttp2/1.57.0
     libarchive version : libarchive 3.7.2 zlib/1.3 liblzma/5.4.4 bz2lib/1.0.8 libzstd/1.5.5
       envs directories : /home/yjx/micromamba/envs
          package cache : /home/yjx/micromamba/pkgs
                          /home/yjx/.mamba/pkgs
            environment : None (not found)
           env location : -
      user config files : /home/yjx/.mambarc
 populated config files : /home/yjx/.condarc
       virtual packages : __unix=0=0
                          __linux=6.1.62=0
                          __glibc=2.38=0
                          __archspec=1=x86_64-v3
               channels : 
       base environment : /home/yjx/micromamba
               platform : linux-64

Logs

No response

environment.yml

No response

~/.condarc

No response