Validate config schema

[bentsherman]

Redo of #4201

This PR uses the config scope classes (in the new compiler module) to validate the config at runtime, for the config and run commands.

Validation occurs after plugins are loaded, and the validator uses the plugin system to collect all implementations of the ConfigScope interface, so plugins can use this interface to declare their config options to Nextflow.

I suggest we merge this in an upcoming release and advise plugin developers to implement this interface before 25.04, to make the transition to next stable as smooth as possible.

This work is also a prerequisite to recognizing third-party plugin config in VS Code.

[netlify]

✅ Deploy Preview for nextflow-docs-staging ready!

Name	Link
🔨 Latest commit	7576572
🔍 Latest deploy log	https://app.netlify.com/sites/nextflow-docs-staging/deploys/67c0b4a811a54600080a9982
😎 Deploy Preview	https://deploy-preview-5816--nextflow-docs-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[bentsherman]

Looking deeper into the failing unit test:

params.foo = 'baz'

profiles {
    test {
        params.foo = 'foo'
        profiles {
            debug {
                cleanup = false
            }
        }
    }
}

the test expects the following resolved config:

params.foo = 'baz'

profiles {
   test {
      params.foo = 'foo'
   }
   debug {
      cleanup = false
   }
}

in other words, the nested profiles block is actually merged with the top profiles block, producing two profiles test and debug.

However, while it works with nextflow config, it doesn't work with nextflow run:

$ nextflow run hello -profile debug

 N E X T F L O W   ~  version 25.01.0-edge

Unknown configuration profile: 'debug'

I think this is an artifact of the ConfigSlurper on which the v1 config parser was based. It was never a documented feature, and the v2 config parser doesn't support it. I think it just makes configs harder to interpret anyway, if profiles can modify other profiles.

The v2 config parser doesn't support nested profiles, so it just warns about a spurious config option:

$ NXF_SYNTAX_PARSER=v2 ./build/releases/nextflow-25.01.0-edge-dist config -a 
WARN: Unrecognized config option 'profiles.debug.cleanup'
params.foo = 'baz'

profiles {
   test {
      params.foo = 'foo'
      profiles {
         debug {
            cleanup = false
         }
      }
   }
}

[bentsherman]

Had to pick some valid config option here. Alternatively we could leave the invalid options and include the warnings for them in the expected stdout