Improve tag and release strategy

[ScottBrenner]

Commits to the 'main' branch should be appropriately tagged into version X.Y.Z and released to the GitHub Marketplace. "minor" and "patch" tags and releases should additionally be tagged and released as "major" release X, replacing the previous "major" release's contents. Changes should be detailed in https://github.com/ScottBrenner/cfn-lint-action/blob/main/CHANGELOG.md.

As a concrete example, 3e2d72a was (manually) tagged and released as both 2.1.0 and 2. This allows people to use this Action as scottbrenner/cfn-lint-action@vX and get all updates in vX.Y.Z without update the minor/patch version they use.

Our current tag and release strategy is coded in https://github.com/ScottBrenner/cfn-lint-action/blob/main/.github/workflows/release.yml and uses https://github.com/ScottBrenner/generate-changelog-action to automatically generate GitHub releases with a changelog as the release's body. Using 3e2d72a as the example, the following steps were taken to tag and release both 2.1.0 and 2. The steps to accomplish this were as follows

1. Merge Re-Introduction of Problem Matchers #43
2. Tag 3e2d72a as v2.1.0
   3. git tag v2.1.0
   4. git push origin v2.1.0
3. Publish https://github.com/ScottBrenner/cfn-lint-action/releases/tag/v2.1.0 to the GitHub Marketplace
   4. https://github.com/ScottBrenner/cfn-lint-action/releases/edit/v2.1.0 ➡️ "Publish this Action to the GitHub Marketplace"
4. Delete the previous v2 tag and release
   4. https://github.com/ScottBrenner/cfn-lint-action/releases/tag/v2 ➡️ "Delete"
5. Tag 3e2d72a as v2.1.0
   6. git tag v2.1.0
   7. git push origin v2.1.0
6. Publish https://github.com/ScottBrenner/cfn-lint-action/releases/tag/v2 to the GitHub Marketplace
   7. https://github.com/ScottBrenner/cfn-lint-action/releases/edit/v2 ➡️ "Publish this Action to the GitHub Marketplace"

Not terribly inconvenient, but pretty manual. It's fun to use https://github.com/ScottBrenner/generate-changelog-action, but does it suit our tag and release strategy or impose on it? https://github.com/semantic-release/semantic-release seems much more .. better. Maybe we can use https://github.com/lob/generate-changelog#recommended for updating https://github.com/ScottBrenner/cfn-lint-action/blob/main/CHANGELOG.md?