[ENH] - Accept misspelling 'dependencies' in env yaml spec

[kcpevey]

Feature description

Apparently if you misspell "dependencies" as "depedencies" in an environment yaml spec, the environment will still solve properly since conda (or conda-lock?) understands the misspelling.

On conda-store this means that if I misspell it in env spec like this:

channels:
- conda-forge
depedencies:
- python=3.10
- pip
- pip:
  - daml
  - numpy
  - scikit-learn

conda-store will solve what I submit as yaml spec, which will solve including those dependencies.

HOWEVER, conda-store drops anything it doesn't understand. Which means that when I go back to view/edit the yaml spec for this environment, it will look like this:

channels:
  - conda-forge
dependencies:
  - ipykernel

I propose that conda-store should accept the fields that conda accepts and correct as needed in order to maintain these fields in the stored spec.

Value and/or benefit

Users who are not confused when they make this mistake :)

Anything else?

No response

[trallard]

This might be a conda-lock thing? In any case, I am -1 on supporting this as it technically is a user mistake and will likely fail if using conda-lock or whatever thing is failing on conda-store elsewhere

[kcpevey]

No problem. I just thought it was a "nice to have".