CI: Single workflow for GitHub and Pypi release

[tomassebestik]

Description

This PR is adding single workflow that creates release:

• release on GitHub
• build packages (python wheels)
• creates release notes from changelog last released version
• uploads builds to GitHub release as assets
• uploads builds to PYPI

Others

• add default CodeQLworkflow for Python

Notes

• if this works well, lets put this workflow to https://github.com/espressif/standards (future repo, org common setup and tools)

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 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.
- 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 6e9f122

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[radimkarnis]

Left a few small notes. Otherwise LGTM!

[radimkarnis]

At this point, you are installing dependencies from the previous version.
I believe it should be python -m pip install pip . --upgrade

[radimkarnis]

nitpick, it should be stylized as PyPI

[radimkarnis]

nitpick: Release_notes.md with a first capital letter seems a little unusual

[peterdragun]

I am a bit confused by this, the versions do not seem to match in the comments and code. Another thing is that it seems that it will build for arm64 macOS twice - on version 12 and 14, but not even once for amd64.