feat(cli): adding logout examples

[gaurangkudale]

adding logout examples for improvement #15690

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).
• The title of the PR conforms to the Toolchain Guide
• 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).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 49.50%. Comparing base (f87897c) to head (be2d168).
Report is 13 commits behind head on master.

❗ Current head be2d168 differs from pull request most recent head e560db2. Consider uploading reports for the commit e560db2 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #15841      +/-   ##
==========================================
- Coverage   49.73%   49.50%   -0.23%     
==========================================
  Files         274      270       -4     
  Lines       48948    47495    -1453     
==========================================
- Hits        24343    23514     -829     
+ Misses      22230    21669     -561     
+ Partials     2375     2312      -63     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gaurangkudale]

If I ran make test then I am getting following error

`error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.
error obtaining VCS status: exit status 128
Use -buildvcs=false to disable VCS stamping.

• which go-junit-report
  /go/bin/go-junit-report
• TEST_RESULTS=test-results
• TEST_FLAGS=
• test '' '!=' ''
• test '' '!=' ''
• mkdir -p test-results
• GODEBUG=tarinsecurepath=0,zipinsecurepath=0
• /go/src/github.com/argoproj/argo-cd/dist/gotestsum --rerun-fails-report=rerunreport.txt --junitfile=test-results/junit.xml --format=testname --rerun-fails=0 --packages= -- -coverprofile=coverage.out
  ./hack/test.sh: line 18: /go/src/github.com/argoproj/argo-cd/dist/gotestsum: No such file or directory
  make: *** [Makefile:388: test-local] Error 127
  make: *** [test] Error 2`

[crenshaw-dev]

Looks like formatting is slightly off. Mind running make lint?

[gaurangkudale]

Hi @crenshaw-dev
If you are free Can you please Review this PR?

[ishitasequeira]

LGTM!