Phantom param mismatch between nextflow.config and nextflow_schema.json

Description of the bug

Hey, I just stumbled across an annoying bug:

1. I have a param vireo_cell_range well defined in both nextflow.config and ǹextflow_schema.json
2. The param is used in modules.config like this
3. When running nf-core pipelines lint I get schema_params: Param vireo_cell_range ! from nextflow config not found in nextflow_schema.json

Now after some debugging (with nf-core pipelines schema build) I realized that params.vireo_cell_range != "all" ? "--cellRange ${params.vireo_cell_range}" : "" is interpreted as a parameter definition, and everything before = goes into the param name and everything afterwards is the default value.

After fixing it with this commit, I still had the same issue. This was because apparantly changes to modules.config do not invalidate the cached representation of the parameters. I had to run rm -rf ~/.nextflow/nf-core additionally to make it work.

Command used and terminal output

System information

nf-core tools version: 3.3.2
nextflow version: 25.04.7.5955

Reproduce the report with nf-core pipelines schema build and nf-core pipelines lint, using the referenced nextflow.config, modules.config, and nextflow_schema.json. Trace how parameter definitions are parsed and cached, then verify that changing modules.config removes the phantom vireo_cell_range mismatch without manually deleting ~/.nextflow/nf-core.