feat(subworkflows): rename utils_nfvalidation_plugin to utils_validate_params

[maxulysse]

Name is more future proof with the coming nf-validation to nf-schema release

PR checklist

Closes #XXX

• This comment contains a description of changes (with reason).
• If you've fixed a bug or added code that should be tested, add tests!
• If you've added a new tool - have you followed the module conventions in the contribution docs
• If necessary, include test data in your PR.
• Remove all TODO statements.
• Emit the versions.yml file.
• Follow the naming conventions.
• Follow the parameters requirements.
• Follow the input/output options guidelines.
• Add a resource label
• Use BioConda and BioContainers if possible to fulfil software requirements.
• Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
  • For modules:
    • nf-core modules test <MODULE> --profile docker
    • nf-core modules test <MODULE> --profile singularity
    • nf-core modules test <MODULE> --profile conda
  • For subworkflows:
    • nf-core subworkflows test <SUBWORKFLOW> --profile docker
    • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
    • nf-core subworkflows test <SUBWORKFLOW> --profile conda

[adamrtalbot]

Personally, I like this more. It says what the subworkflow does and not what it is, which is way easier to understand.

I think a name is a part of the API, therefore it should remain static while the internals freely change.

But I'd like someone else's opinion!

[SPPearce]

Why is this utils_utils_validate_params not just utils_validate_params?

[maxulysse]

Why is this utils_utils_validate_params not just utils_validate_params?

That was a typo, sorry about that...
🤦

[SPPearce]

Are we happy with the name?

[mashehu]

this was in the template for a bit. can we wait until we have some functionality in tools to handle a rename gracefully?