use -V (upper case) for --version short form

[pmeier]

Reference Issues or PRs

Fixes #1719.

What does this implement/fix?

Put a x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

• Did you test the pull request locally?
• Did you add new tests?

Any other comments?

This could be considered BC breaking, but I feel that would be a tad too much.

[pavithraes]

@iameskild @pmeier -- Would this be a breaking/surprising change for existing users? If so, maybe can have a deprecation warning or an error message for the lowercse -v as we change this behavior?

[pmeier]

Would this be a breaking

Technically, yes.

surprising change for existing users

IMHO, no. As explained in #1719, with this change, our CLI is less surprising than before.

If so, maybe can have a deprecation warning or an error message for the lowercse -v as we change this behavior?

We could, but I wouldn't recommend it. For the reasons above and since we don't even have a BC policy as of now, I don't see the point. LMK if folks feel otherwise. Deprecation is not hard to implement here.