Fix CLI params normalization

[bentsherman]

Close #5655

[netlify]

✅ Deploy Preview for nextflow-docs-staging canceled.

Name	Link
🔨 Latest commit	57f7e58
🔍 Latest deploy log	https://app.netlify.com/sites/nextflow-docs-staging/deploys/677ff1ec197bf00008b12c3f

[pditommaso]

There should be a test that validates the solution

[bentsherman]

I have updated the tests accordingly

[pditommaso]

Not following much, the issue says

I would expect to see this output (according to https://github.com/nextflow-io/nextflow/pull/4702):

[thingOne:newval]
newval
But instead I see this:

[thing-one:newval, thingOne:nothing]
nothing

I would expect, the test to validate the correct behaviour, instead only add quotes to some numeric values

[bentsherman]

Check again, it also changed addParam0 to addParam in order to test the full behavior

[pditommaso]

Continue to not understand how the test validates the fix for the defect reported.

[bentsherman]

Discussed internally. Here's the red-green analysis to show how the unit test captures the original problem.

Without the changes to CmdRun, the test fails as follows:

Condition not satisfied:

params['alphaBeta'] == 10
|     |             |
|     1             false
[alphaBeta:1, alpha-beta:10]

	at nextflow.cli.CmdRunTest.should convert cli params from kebab case to camel case(CmdRunTest.groovy:105)

Note that alphaBeta is set first, then alpha-beta which should be converted to alphaBeta and override the previous setting.

With the changes to CmdRun, the tests pass as shown in CI.