feat(tags): adds `legacy_tag_formats` and `ignored_tag_formats` settings

Description

This PR add 2 new settings to handle tag formats;

legacy_tag_formats allowing tag format to change over time while retaining the ability to work with legacy version
ignored_tag_formats to specify expected tag that should not raise InvalidVersion.

So projects which change tag formats and have expected but non-version tags can have these settings:

tag_format = "v${version}"
legacy_tag_formats = [
    "${version}",
    "project-prefix-${version}",
]
ignored_tag_formats = [
    "stable",
    "other-project-*",
]

By doing so, I had to start grouping tag handling and introduce a tags.TagRules object which is responsible for handling all tags rules, initially spread over tag_format, version_schemes and version_providers

Checklist

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

Expected behavior

I can change tag format and still being able to:
- bump versions (aka. find the increment and commits range)
- generate changelog (full, incremental, version range)
I can generate a changelog without warnings for expected tags

Steps to Test This Pull Request

create a project
set version_provider = "scm" (not mandatory but allows testing the full scope)
bump some versions with an initial tag_format
move current tag_format in legacy_tag_format and define a new tag_format
bump a version with changelog:
- current version should be properly identified
- increment should properly been found
- new version should be correct
- generated changelog generation should be correct (both new and old version formats)
- new tag should respect the new tag_format

then:

add random-* to ignored_tag_formats
tag any commit with random-tag
run cz changelog
- there shouldn't be any warning

Additional context

There might be a 2nd PR handling a changelog_version_format setting to customize the version rendering in the changelog so:

it's not the tag format anymore (problematic with some prefixes, like for monorepos)
have a uniform version display across tag_format changes

Codecov Report

Attention: Patch coverage is 99.43182% with 1 line in your changes missing coverage. Please review.

Project coverage is 97.65%. Comparing base (120d514) to head (6eeeb41). Report is 496 commits behind head on master.

Files with missing lines	Patch %	Lines
commitizen/commands/bump.py	92.85%	1 Missing :warning:

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #1297 +/- ## ========================================== + Coverage 97.33% 97.65% +0.32% ========================================== Files 42 56 +14 Lines 2104 2606 +502 ========================================== + Hits 2048 2545 +497 - Misses 56 61 +5 ``` | [Flag](https://app.codecov.io/gh/commitizen-tools/commitizen/pull/1297/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=None) | Coverage Δ | | |---|---|---| | [unittests](https://app.codecov.io/gh/commitizen-tools/commitizen/pull/1297/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=None) | `97.65% <99.43%> (+0.32%)` | :arrow_up: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=None#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

commitizen-tools / commitizen