cli: fixes bug where the wrong exit status is reported

[RuvendeGroote]

Fixes: #2117

[vercel]

@RuvenSalamon is attempting to deploy a commit to the coral-xyz Team on Vercel.

A member of the Team first needs to authorize it.

[Henry-E]

Ok, so this is linked to how AVM processes CLI calls and sends them to whatever version of anchor is active.

Don't forget to add a changelog.

[RuvendeGroote]

Ok, so this is linked to how AVM processes CLI calls and sends them to whatever version of anchor is active.

Don't forget to add a changelog.

Done!

[Henry-E]

Dumb question but how can i verify / test that this doesn't just break AVM. I'm not sure if avm has tests or if the tests use avm for their CLI stuff. I only ask because I assume this is something you've tested locally in order to verify that it works?

[RuvendeGroote]

Dumb question but how can i verify / test that this doesn't just break AVM. I'm not sure if avm has tests or if the tests use avm for their CLI stuff. I only ask because I assume this is something you've tested locally in order to verify that it works?

I basically compiled and ran the executable from the target dir. I do see some tests executing the anchor command in the tests dir (although it seems to use anchor from the ts package and not the avm wrapper) but no tests for avm in the avm dir.
I can add a test if you want, not sure if you'd like them in the tests folder as that seems to also function as a sort of repository of examples and this would not really be an example. I could create a tests dir in the avm dir?
I will be away during the weekend so might be slow to react. Will fix the conflict as well (unless somebody else wants to do these things)

[RuvendeGroote]

(Accidentally closed the PR, misclick)