2.0.2 return non zero for bad usage

[corwinsheahan-wf]

Motivation

Back patch of this PR to the 2.x release line.

Changes

• Cherry pick changes from that ^ PR.
• Ran format under dart 2.14.4

  Release Notes

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:

QA Checklist

• [ ] Tests were updated and provide good coverage of the changeset and other affected code
• [ ] Manual testing was performed if needed
  • [ ] Steps from PR author:
  • [ ] Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• [ ] A Client Platform member has reviewed these changes
• [ ] There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• [ ] For release PRs - Version metadata in Rosie comment is correct

[aviary3-wk]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure

• Verify aviary.yaml coverage of security relevant code

  Questions or Comments? Reach out on Slack: #support-infosec.

[corwinsheahan-wf]

@evanweible-wf Done

[evanweible-wf]

Just noticed that the GitHub CI checks aren't running because we hadn't switched over from Travis CI on v2 yet. Tried running the tests locally, but I'm seeing some failures.. looking into it

[evanweible-wf]

QA +1

• [x] Ran tests locally and they passed (after adding the meta: <1.7.0 workaround which is only needed for local dev)

@Workiva/release-management-p