Not possible to pass array of values for envs with local runner (cli)

[DariuszPorowski]

Describe the bug
Not possible to pass array of values for envs with local runner. According to docs https://megalinter.io/latest/mega-linter-runner/#examples it should be supported.

To Reproduce
Steps to reproduce the behavior:

run local runner (cli):

mega-linter-runner -e 'ENABLE=MARKDOWN,YAML'

Behind the hood, the runner splits env to two different docker envs.

docker run -e ENABLE=MARKDOWN -e YAML oxsecurity/megalinter-documentation:v6

and megalinter runs only MARKDOWN linter

Expected behavior
A clear and concise description of what you expected to happen.

MARKDOWN and YAML linters shoud run both, and docker command should looks like:

docker run -e ENABLE=MARKDOWN,YAML oxsecurity/megalinter-documentation:v6

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Probably this causes the issue:

megalinter/mega-linter-runner/lib/options.js

Line 22 in 1d15a5e

concatRepeatedArrays: true,

according to lib's doc: https://github.com/gkz/optionator#option-properties

concatRepeatedArrays is an optional boolean or tuple with boolean and options object (defaults to false) - when set to true and an option contains an array value and is repeated, the subsequent values for the flag will be appended rather than overwriting the original value - eg. option g of type [String]: -g a -g b -g c,d will result in ['a','b','c','d']

or lib's default value for aliasSeparator

https://github.com/gkz/optionator/blob/master/README.md#help-style-properties

[Kurt-von-Laven]

Duplicate of #1659. I won't close this though since we will gladly accept a PR to correct the documentation.

[echoix]

@Kurt-von-Laven has beaten me and found the other related issue before me. Especially see the resolution here #1659 (comment)

[DariuszPorowski]

@Kurt-von-Laven @echoix oh! Thank you, I tried to review some issues first and cannot find it. Used ENABLE keyword instead of DISABLE ;) Solution from #1659 works.