Separate CLI from runtime

[bentsherman]

This PR splits the nextflow module into two modules:

• nextflow: contains only the Launcher and CLI classes
• nf-runtime: contains everything (i.e. the "runtime")

Benefits:

• Improves build time, editing CLI code doesn't rebuild the entire project
• Removes some circular dependencies, making the code easier to read/understand
• Library consumers like platform or plugins can just depend on the runtime and not the CLI
• Makes it easier to implement a CLI v2 in the future

I left ConfigBuilder in the CLI module for now because it is a tangled mess. In a follow-up PR I would like to separate the "core" ConfigBuilder from the extra CLI logic (e.g. ConfigCliAdapter)

Note to self: could also keep nextflow as it is and move the CLI code into a separate module e.g. nextflow-cli.

[bentsherman]

Due to the nature of this PR, I will keep it updated via rebase instead of merge commits so that the changes are as clear as possible.

[pditommaso]

oh mamma mia 😆

[bentsherman]

Your k8s plugin inspired me 😄

[pditommaso]

I feared that 😆

[bentsherman]

Jokes aside, it might be good to do the actual code changes in a separate PR so that the nf-runtime part is as clean as possible

The nf-runtime refactor was just the easiest way to reveal the circular dependencies

[pditommaso]

I'll review post 25.04

[bentsherman]

Refactored so that the CLI code is in a new module nf-cli-v1. Made the PR considerably smaller

Note the following plugins depend explicitly on the CLI code because they add CLI commands:

• nf-console
• nf-k8s
• nf-tower
• nf-wave

Might be possible to remove this dependency by moving some interfaces into the core runtime, but not a big deal either way