docs: unified option format

[cleverhu]

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).

[codecov]

Codecov Report

Patch coverage has no change and project coverage change: -0.02 ⚠️

Comparison is base (5976d70) 49.77% compared to head (4a9cfe5) 49.75%.

❗ Current head 4a9cfe5 differs from pull request most recent head 80a5794. Consider uploading reports for the commit 80a5794 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #11257      +/-   ##
==========================================
- Coverage   49.77%   49.75%   -0.02%     
==========================================
  Files         261      261              
  Lines       44653    44653              
==========================================
- Hits        22225    22219       -6     
- Misses      20246    20250       +4     
- Partials     2182     2184       +2     

Impacted Files	Coverage Δ
cmd/argocd/commands/account.go	0.00% <0.00%> (ø)

... and 2 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[fengshunli]

@crenshaw-dev @alexef can be merged