output help information when dapr has no parameters

[tianyax]

Description

Fixed the problem that the output of the dapr did not match the documentation after installation.

Issue reference

We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.

Please reference the issue this PR will close: #1254

Checklist

Please make sure you've completed the relevant tasks for this PR, out of the following list:

• Code compiles correctly
• Created/updated tests
• Extended the documentation

[tianyax]

local validation results:

[codecov]

Codecov Report

Merging #1255 (814d6ec) into master (5e3546a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1255   +/-   ##
=======================================
  Coverage   27.27%   27.27%           
=======================================
  Files          38       38           
  Lines        3711     3711           
=======================================
  Hits         1012     1012           
  Misses       2633     2633           
  Partials       66       66           

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[shubham1172]

The --version flag should be the same as dapr version IMO. It is meaningful to provide both CLI and installed runtime's version.

[tianyax]

The --version flag should be the same as dapr version IMO. It is meaningful to provide both CLI and installed runtime's version.

@shubham1172 For --version flag I think in most cases it should print its own information, and it overlaps with the dapr version function, I respect the original design and will make a change.😊

[mukundansundar]

LGTM

changes addressed.

[mukundansundar]

@tianyax Thanks for the contribution, welcome to the Dapr community.