fix: Set exitcode of secrets-config for command execution errors

[bnevis-i]

Closes #4337

PR Checklist

Please check if your PR fulfills the following requirements:

• I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
• I am not introducing a new dependency (add notes below if you are)
• I have added unit tests for the new feature or bug fix (if not, why?)
• I have fully tested (add details below) this the new feature or bug fix (if not, why?)
• I have opened a PR for the related docs change (if not, why?)

Testing Instructions

See use cases in #4337 for sample test cases to try to verify issue is fixed.

New Dependency Instructions (If applicable)

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[bnevis-i]

@farshidtz Please review this one-line fix.

[farshidtz]

I can't reproduce any of the previous errors because that functionality no longer exists.
I did do some sanity checks and the error codes seem correct.

[farshidtz]

I don't know if this is a bug or feature. I noticed that the -jwtTTL takes both integer and go duration but not sure they both get accepted or if one is ignored.

$ sudo edgexfoundry.secrets-config proxy adduser --user example -useRootToken -jwtTTL 4
{"username":"example","password":"TYMMvc80BGdqYOu55VPIru8z4Ibr/ryytopuzd5nAQ2X"}

$ sudo edgexfoundry.secrets-config proxy adduser --user example -useRootToken -jwtTTL 4h
{"username":"example","password":"Kx2mBBwYRXo9HOC7SUUPrlrYoQowexC/S5k7rie32cNG"}

Given the description below, I expect only Go duration to be supported. Go's time.Duration rejects integer input: https://go.dev/play/p/E9nNy8Sw7pi

  -jwtTTL string
    	JWT created by vault identity provider lasts this long (default "1h")

[bnevis-i]

I don't know if this is a bug or feature. I noticed that the -jwtTTL takes both integer and go duration but not sure they both get accepted or if one is ignored.

$ sudo edgexfoundry.secrets-config proxy adduser --user example -useRootToken -jwtTTL 4
{"username":"example","password":"TYMMvc80BGdqYOu55VPIru8z4Ibr/ryytopuzd5nAQ2X"}

$ sudo edgexfoundry.secrets-config proxy adduser --user example -useRootToken -jwtTTL 4h
{"username":"example","password":"Kx2mBBwYRXo9HOC7SUUPrlrYoQowexC/S5k7rie32cNG"}

Given the description below, I expect only Go duration to be supported. Go's time.Duration rejects integer input: https://go.dev/play/p/E9nNy8Sw7pi

  -jwtTTL string
    	JWT created by vault identity provider lasts this long (default "1h")

proxy tls --incert --inkey would fail in the same way if pointed to nonexistent files.

[bnevis-i]

@farshidtz

Turns out I pass it directly to vault. https://developer.hashicorp.com/vault/docs/concepts/duration-format

--jwtTTL 5 turns out to be 5 SECONDS!

Will update command line help.