feat(plugin): add plugin, commit message questions, changelog template

[tomassebestik]

Description

This is commitizen plugin with Espressif standards already set

• no need long and messy config in pyproject.toml for commitizen
• unify way of nice looking changelog that fits for most Espressif projects
• some customizations with cz_customize never worked anyway (order in changelog, types to changelog) - this is now possible
• only package czespressif put in development dependecies, it will download commitziten automatically
• very minimum setup in pyproject.toml is necessary, but quite a lot of options to customize

Features

• reads options from target project "pyproject.toml"
• changelog mapping dynamically from types
• switch for disable emoji from target project "pyproject.toml"
• configured bump_pattern and bump_map for changelog
• add commit parser passing conventional-commit-linter rules and changelog hooks
• switch for disable section "Unreleased" from target project "pyproject.toml"
• "change_type_order" possible set from from target project "pyproject.toml"
• add "cz info" (short info) and "cz example" (full example) to the CLI commands
• ci: versions from scm_tools
• ci: updated to support Python 3.9

Try it

In any repo with conventional commits pip install czespressif and add to pyproject.toml:

[tool.commitizen]
  name            = "czespressif"

Then try cz changelog to compare how current changelog was updated (it will not commit, just changes local file; be sure you have CHANGELOG.md staged).

Other commands updated by this plugin: cz commit, cz bump --dry-run, cz example, cz info

Related

Testing

---

Checklist

Before submitting a Pull Request, please ensure the following:

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• Documentation is updated as needed.
• Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.

[github-actions]

	Warnings
⚠️	Please consider squashing your 15 commits (simplifying branch history).

	Messages
📖	This PR seems to be quite large (total lines of code: 1208), you might consider splitting it into smaller PRs

👋 Hello tomassebestik, we appreciate your contribution to this project!

---

📘 Please review the project's Contributions Guide for key guidelines on code, documentation, testing, and more.

---

Click to see more instructions ...

This automated output is generated by the PR linter DangerJS, which checks if your Pull Request meets the project's requirements and helps you fix potential issues.

DangerJS is triggered with each push event to a Pull Request and modify the contents of this comment.

Please consider the following:
- Danger mainly focuses on the PR structure and formatting and can't understand the meaning behind your code or changes.
- Danger is not a substitute for human code reviews; it's still important to request a code review from your colleagues.
- Resolve all warnings (⚠️ ) before requesting a review from human reviewers - they will appreciate it.
- Addressing info messages (📖) is strongly recommended; they're less critical but valuable.
- To manually retry these Danger checks, please navigate to the Actions tab and re-run last Danger workflow.

Review and merge process you can expect ...

We do welcome contributions in the form of bug reports, feature requests and pull requests.

1. An internal issue has been created for the PR, we assign it to the relevant engineer.
2. They review the PR and either approve it or ask you for changes or clarifications.
3. Once the GitHub PR is approved we do the final review, collect approvals from core owners and make sure all the automated tests are passing.
- At this point we may do some adjustments to the proposed change, or extend it by adding tests or documentation.
4. If the change is approved and passes the tests it is merged into the default branch.

Generated by 🚫 dangerJS against 7e5377f

[hfudev]

Cool. LGTM