Add snake_case to params normalization

[ahvigil]

fixes #3878. There are two changes here:

• snake_case pipeline param names are now handled in a way that is consistent with what nextflow does for kebab-case and camelCase params, which are already interchangeable on the command line. That means --long-name, --longName, and --long_name are parsed as the same param.
• change the way param names get normalized so that instead of storing duplicate entries in the ParamsMap for each parameter representation, we normalize before accessing the underlying map. With the previous implementation, ParamsMap('foo-bar':1) produces a ParamsMap of size 2, which seems kind of confusing.

[ahvigil]

this test case changes because camel case is a bit ambiguous with numbers- field-1 normalizes to field1 but field1 wasn't converting via camelCaseToHyphen into field-1.

[ahvigil]

ParamsMap.size now more accurately reflects the number of params it contains.

[ahvigil]

CLI is being rewritten in #3600 so this code will soon be deprecated, closing

[bentsherman]

Since the params normalization code is separate from the CLI, it should not be affected by the new CLI, so let's keep this open.

However I would prefer to merge this fix #4188 first.

[netlify]

✅ Deploy Preview for nextflow-docs-staging ready!

Name	Link
🔨 Latest commit	753ad9d
🔍 Latest deploy log	https://app.netlify.com/sites/nextflow-docs-staging/deploys/65ae96d284b29f0008ec7ee5
😎 Deploy Preview	https://deploy-preview-3884--nextflow-docs-staging.netlify.app/cli
📱 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.

[ahvigil]

updated with merge from master to incorporate changes from #4188 with necessary updates, and made a small update to mention in the docs

[Nish9]

Looks like this is not merged. Any idea when this feature will be available?

[bentsherman]

Unfortunately I don't think this will be merged soon because the params are being overhauled (#4669) and this change would likely need to be incorporated into that. Feel free to comment there to share your thoughts.

I have been thinking about snake case though, and I think, if we have a params schema then we can intelligently convert kebab-case CLI params to either snake-case or camel-case depending on whether that param is defined in the schema.

Also there is no need to keep the kebab-case params in the params map for the script since you wouldn't access those anyway (see #4702)