Exit with usage code when incorrect args are used

[corwinsheahan-wf]

Motivation

When non-recognized args are used, we print the help message, but still exit with a 0 exit code. This can cause false positives in CI if legacy command line args are used.

Changes

• Return appropriate exit code
• Add test

  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

[aviary-wf]

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.

[evanweible-wf]

@corwinsheahan-wf could you add a changelog entry and run formatter on dart 2.14.4?

[corwinsheahan-wf]

@evanweible-wf Updated.

[evanweible-wf]

QA +1

@Workiva/release-management-pp