feat(cli): add config option to specify config file path

[rockleona]

Description

CLI now have an option --config can specify the config file path,
if the config file is not in root folder, user can specify the located file as well.

Checklist

• Add test cases to all the changes you introduce
• Run ./scripts/format and ./scripts/test locally to ensure this change passes linter check and test
• Test the changes on the local machine manually
• Update the documentation for the changes

Expected behavior

cz now have an option to specify config file,
if the given file is existed, will only read configuration from the given file,
else, a error would be raise since the given file do not exist.

Steps to Test This Pull Request

Execute any cz command with --config option, if the config file do not exist, a error would raised.

Additional context

resolve #656

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.50%. Comparing base (120d514) to head (bf6a6bf).
Report is 260 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1047      +/-   ##
==========================================
+ Coverage   97.33%   97.50%   +0.16%     
==========================================
  Files          42       55      +13     
  Lines        2104     2446     +342     
==========================================
+ Hits         2048     2385     +337     
- Misses         56       61       +5     

Flag	Coverage Δ
unittests	97.50% <100.00%> (+0.16%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[woile]

What's the motivation for this change?

[rockleona]

What's the motivation for this change?

Simply just found out #656 is quite interesting for me,
but actually I can not imagine about the usage or in what scenario user will use this option.

[Lee-W]

What's the motivation for this change?

Simply just found out #656 is quite interesting for me, but actually I can not imagine about the usage or in what scenario user will use this option.

Someone who wants to use a single config for all projects might need it. or mono repo maybe?

[Lee-W]

Hi @rockleona, thanks so much for implementing this. I left a few comments.

[Lee-W]

I think we're really close to merging! In addition to the comment to address, I would suggest you squash the latest 2 commits into the first one as they're minor fixes and do not really need to appear in the changelog. Thanks!

[Lee-W]

LGTM. @woile @noirbizarre I'll merge this one these days. Please let me know if you want to take a deeper look

[noirbizarre]

Good to me.

Non blocking suggestion: test and ensure that user home path expansion works (users WILL use home-relative forms for sure so handling cases like ~/path/to/config from start will avoid inevitable issues)

[Lee-W]

Good to me.

Non blocking suggestion: test and ensure that user home path expansion works (users WILL use home-relative forms for sure so handling cases like ~/path/to/config from start will avoid inevitable issues)

Tested on my end. Works fine. Gonna merge it 🚀