nf-core modules install support non nf-core structured pipelines

Description of feature

nf-core modules does not support importing from a modules repo or pipeline that does not conform to nf-core standards:

> nf-core modules --git-remote https://github.com/genepi/nf-gwas list remote

                                          ,--./,-.
          ___     __   __   __   ___     /,-._.--~\
    |\ | |__  __ /  ` /  \ |__) |__         }  {
    | \| |       \__, \__/ |  \ |___     \`-._,-`-,
                                          `._,._,'

    nf-core/tools version 2.9 - https://nf-co.re


CRITICAL 'org_path' key not present in .nf-core.yml 

> nf-core modules --git-remote https://github.com/epi2me-labs/wf-basecalling list remote

                                          ,--./,-.
          ___     __   __   __   ___     /,-._.--~\
    |\ | |__  __ /  ` /  \ |__) |__         }  {
    | \| |       \__, \__/ |  \ |___     \`-._,-`-,
                                          `._,._,'

    nf-core/tools version 2.9 - https://nf-co.re


CRITICAL 'org_path' key not present in .nf-core.yml     

We should support importing from other Nextflow pipelines that are hosted elsewhere.

There are lots of places that could go wrong. It sounds like a nightmare. See https://github.com/nextflow-io/nextflow/issues/4112 for a discussion about adding this to Nextflow.

Start with the nf-core modules --git-remote command and reproduce the failures against genepi/nf-gwas and epi2me-labs/wf-basecalling. Read the linked Nextflow issue for the discussed constraints; done means non-nf-core hosted pipelines can be imported without the .nf-core.yml org_path error.