Publish a GitHub action that will allow us to generate a conda-lock file

[millsks]

Checklist

• I added a descriptive title
• I searched open requests and couldn't find a duplicate

What is the idea?

We are using conda-lock to create the environment lock files locally as part of our project. It would be great if a GitHub action existed where it could generate a conda-lock file as part of our E2E testing that is kicked off through a workflow on GitHub.

Why is this needed?

It would allow the conda environment to be captured and recreated through a lock file after it was tested. It would help to guarantee that the conda environment is stable and reproducible no matter where it was deployed to.

What should happen?

A GitHub action would be published that will can be used by others to include in their workflow. The result would be a lock file that can be created and added back into the repo prior to creating a tagged release.

Additional Context

No response