Description

If there is already a config file with wrong format in cwd, cz would failed to parse and the exception is unhandled. #729 have fixed that for json config, but yaml and toml are not.

Fixes #577

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 should report there is an error when parsing config file.

Steps to Test This Pull Request

Execute following commands:

mkdir /tmp/cz-init
cd /tmp/init
echo 'i am not toml' > .cz.toml
# or test yaml format
# echo 'i: am: not: yaml' > .cz.yaml
cz init

and you will see error message like this:

Failed to parse .cz.toml: Invalid key "invalid content" at line 1 col 15

or this:

Failed to parse .cz.yaml: mapping values are not allowed here
 in "<byte string>", line 1, column 6:
 i: am: not: yaml
 ^

Additional context