Nextflow inspect does not accept workDir on command line

[adamrtalbot]

Bug report

Expected behavior and actual behavior

When using nextflow inspect, it does not accept the workdir on the command line (-w work) which can be annoying for using it, especially on cloud environments where you have to provide a remote path (s3/gs/az).

Steps to reproduce the problem

> nextflow inspect hello -w work
Unknown option: -w -- Check the available commands and options and syntax with 'help'

Instead it should go...

> nextflow inspect . -w work
{
    "processes": [
        {
            "name": "sayHello",
            "container": "docker.io/library/ubuntu:23.10"
        }
    ]
}

nextflow inspect hello -w work

nextflow inspect hello
{
    "processes": [
        {
            "name": "sayHello",
            "container": "docker.io/library/ubuntu:23.10"
        }
    ]
}

Program output

errr see above.

Environment

• Nextflow version: version 23.10.1 build 5891
• Java version: openjdk version "17.0.8.1" 2023-08-24
• Operating system: all (macOS)
• Bash version: zsh 5.9 (x86_64-apple-darwin23.0)

Additional context

(Add any other context about the problem here)

[adamrtalbot]

We could also just drop the requirement for a working dir altogether with inspect...

[bentsherman]

I don't think the inspect command needs to know the work directory