new feature: make sure conda env is intact for usage

[mewu3]

New feature

Is it possible to have a way to verify the conda environment is intact before launching the pipeline? There are times that the creation of the conda environments fail without (me) notice, the next time i launch, nextflow would assume the env is created and go along with the broken environments. If the env is used in the modules with error ignore, it would take ages for people to find out that failure of the error ignre step is due to conda

Use case

Make sure conda env is indeed correctly created

Suggested implementation

[bentsherman]

@pditommaso I think it would be useful to extend the inspect command to also show the conda environment for each process, and even build every conda environment beforehand

[pditommaso]

Yeah, indeed. Irrespective of that it could done a minimal validation of conda directive content for example checking package name does not contain invalid char, trailing spaces, etc