SM-774: Write Help Text to 'stderr' When No Args Are Provided

[coltonhurst]

Type of change

- [ ] Bug fix
- [ ] New feature development
- [x] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

When no arguments are provided to bws, we should write the help text to stderr rather than stdout to be consistent with the existing bws subcommand behavior.

Potentially relevant clap GitHub discussions:

• feat: Allow users to render usage, help, and errors with ANSI clap-rs/clap#4248
• Add option to print help to stderr clap-rs/clap#3289
• Allow more flexible configuration of the output steam (stdout vs. stderr) clap-rs/clap#1788

Code changes

• main.rs: Print with eprintln

Before you submit

• Please add unit tests where it makes sense to do so (encouraged but not required)

[bitwarden-bot]

Checkmarx One – Scan Summary & Details – e5847bdf-e3dc-447e-8baf-f6f903f5d2e4

No New Or Fixed Issues Found

[Hinton]

I think this changes bws to be more consistent with bws subcommand. So from that perspective I'm fine with this change. We don't want to change --help though.

@dani-garcia any thoughts?

We should document this in the changelog though. Not sure if this qualifies as a breaking change, I have a hard time imagining someone depending on the stdout output when not using any commands.

[coltonhurst]

I think this changes bws to be more consistent with bws subcommand. So from that perspective I'm fine with this change. We don't want to change --help though.

@dani-garcia any thoughts?

We should document this in the changelog though. Not sure if this qualifies as a breaking change, I have a hard time imagining someone depending on the stdout output when not using any commands.

Yes, this should unify our output to stderr in these cases, with the exception when --help is provided.

I have updated the changelog in 669db02.