ABP CLI - Throw exceptions instead swallowing

[enisn]

Description

ABP CLI exit code is always 0 even if there is an error. When it's used in pipeline (abp install-libs), or it's called by another program (abpdev in my case), errors can't be recognized.

Exit code 0 here 👆

So, I threw the exception instead of swallowing it. And now, when a command fails in ABP CLI, it can be handled programmatically.

Checklist

• I fully tested it as developer / designer and created unit / integration tests
• I documented it (or no need to document or I will create a separate documentation issue)

How to test it?

Please describe how this can be tested by the test engineers if it is not already explicit - or remove this section if no need to description.

[codecov]

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (b95482b) 51.72% compared to head (fd99894) 51.72%.
Report is 66 commits behind head on dev.

Files	Patch %	Lines
...k/src/Volo.Abp.Cli.Core/Volo/Abp/Cli/CliService.cs	0.00%	1 Missing ⚠️
...bp.Cli.Core/Volo/Abp/Cli/Commands/BundleCommand.cs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##              dev   #18519   +/-   ##
=======================================
  Coverage   51.72%   51.72%           
=======================================
  Files        3075     3075           
  Lines       96860    96949   +89     
  Branches     7711     7719    +8     
=======================================
+ Hits        50096    50146   +50     
- Misses      45232    45268   +36     
- Partials     1532     1535    +3     

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