Conflicting `--validators-keystore-locking-enabled=false` has Teku complain about `--ee-endpoint`

Description

When adding --validators-keystore-locking-enabled=false to Teku startup parameters, while mistakenly not removing --validators-keystore-locking-enabled=true, it complains that FATAL - Invalid configuration. --ee-endpoint parameter is mandatory when Bellatrix milestone is enabled

Which is unexpected to say the least. A more fitting error message about conflicting parameters would be helpful.

Command line as shown by ps -aux | grep teku:

tech.pegasys.teku.Teku --data-path=/var/lib/teku --log-destination=CONSOLE --network=goerli --ee-endpoint=http://execution:8551 --ee-jwt-secret-file /var/lib/teku/ee-secret/jwtsecret --p2p-port=9020 --p2p-peer-upper-bound=100 --p2p-peer-lower-bound=64 --validators-keystore-locking-enabled=true --validator-keys=/var/lib/teku/validator-keys:/var/lib/teku/validator-passwords --validators-graffiti=🐼eth-docker🐼 --logging=info --rest-api-host-allowlist=* --rest-api-enabled=true --rest-api-interface=0.0.0.0 --rest-api-port=5052 --metrics-enabled=true --metrics-port=8008 --metrics-interface=0.0.0.0 --metrics-host-allowlist=* --validator-api-enabled=true --validator-api-interface=0.0.0.0 --validator-api-port=7500 --validator-api-host-allowlist=* --validator-api-cors-origins=* --validator-api-keystore-file=/var/lib/teku/teku-keyapi.keystore --validator-api-keystore-password-file=/var/lib/teku/teku-keyapi.password --validators-proposer-default-fee-recipient=0x9a1431df76aBF98cbAe0865927a5Ca23d46C3F04 --validators-keystore-locking-enabled=false --validators-builder-registration-default-enabled --builder-endpoint=http://mev-boost:18550 --metrics-publish-endpoint=https://beaconcha.in/api/v1/client/metrics?apikey=SOSECRET&machine=fnurble

Versions (Add all that apply)

• Software version: teku/v22.8.2/linux-x86_64/-eclipseadoptium-openjdk64bitservervm-java-17

[tbenr]

I tried approaching it by adding another pass which sorts the provided params by matched group, but it’s not that straight forward…

[rolfyone]

Basically we need to stop using arggroups, and still get help text out in a nice format. We could create a custom help printer potentially, also potentially could change picocli to allow us to specify headings on mixins or something. The test code in the picocli ticket shows pretty well the problem.