Description

This PR adds the option of setting include_path and exclude_path in the config file.

Motivation and Context

Closes #1168.
This is useful if you have tools calling git-cliff (like release-plz) that don't give the ability
to set command line arguments.

How Has This Been Tested?

Testing exclude_path

1. Run git-cliff | wc -l and note the amount of lines
2. Run git-cliff --exclude-path git-cliff-core/ | wc -l and note the amount of lines
3. Set exclude-paths = ["git-cliff-core/"]
4. Run git-cliff | wc -l and note the amount of lines
   The output of step 4 should equal the output of step 2 and not equal the output of step 1

Testing include_path

1. Run git-cliff | wc -l and note the amount of lines
2. Run git-cliff --include-path git-cliff/ --include-path git-cliff-core/ | wc -l and note the amount of lines
3. Set include_paths = ["git-cliff/", "git-cliff-core/"]
4. Run git-cliff | wc -l and note the amount of lines
   The output of step 4 should equal the output of step 2 and not equal the output of step 1

Both tests were run in the root of the git-cliff repository on a Linux machine.

I could not figure out how to mock commits with changed files and thus have not written any unit/integration tests.

Types of Changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (no code change)
• Refactor (refactoring production code)
• Other

Checklist:

• My code follows the code style of this project.
• I have updated the documentation accordingly.
• I have formatted the code with rustfmt.
• I checked the lints with clippy.
• I have added tests to cover my changes.
• All new and existing tests passed.