[SPIKE] "pepr build --version <version>" writes pepr version to stdout

[btlghrants]

Background

While working #1654 I discovered that when trying to use the --version option we appear to just get the result of pepr --version (almost like Commander.js is interpreting the --version flag overly-eagerly & not letting the sub command parse it..?).

This should be investigated. Current behavior codified in (upcoming) integration test for the pepr build cli:

• /integration/cli/build.version.test.ts : build > builds a module > using a specified pepr version > builds

Definition of Done

1. figure out whether this is a "real" error or just a matter of test setup / config, and
2. fix the error (if it is one).

[samayer12]

Blocked waiting on #1642 to merge with main since integration/cli does not exist on main.

[samayer12]

While working on this, I noticed some test flakes on my dev environment. I've created https://github.com/defenseunicorns/pepr/tree/hotfix-local-integration-failure to dig into the root cause here before I make progress on this issue.

[samayer12]

It turns out --version is used in multiple locations and this indicates an issue with our CLI option parsing. See Pepr Docs.

 npx pepr --help

Options:
  -V, --version   output the version number

versus

npx pepr build --help

Options:
[...]
  -v, --version <version>  The version of the Pepr image to use in the deployment manifests. Example: '0.27.3'.

This internal slack thread discusses options, to include removing the flag if users don't use it.

[samayer12]

Identified some specific follow-on work after taking a look at this issue. Closing and will get to the underlying issues in #1724 and #1725.