Changes from upstream

[Jason2866]

This change fixes the following bug(s):

I have tested this change with the following hardware & software combinations:

I have run the esptool.py automated integration tests with this change and the above hardware:

[github-actions]

	Warnings
⚠️	Some issues found for the commit messages in this PR: the commit message "Auto update version with GH release action": summary looks empty type/action looks empty the commit message "Create gen_pio_manifest.py": summary looks empty type/action looks empty the commit message "Create pack_python.py": summary looks empty type/action looks empty the commit message "Create patch_dev_release.py": summary looks empty type/action looks empty the commit message "Fix if compare": summary looks empty type/action looks empty the commit message "Fix path": summary looks empty type/action looks empty the commit message "Tasmota changes": summary looks empty type/action looks empty the commit message "Update .cz.toml": summary looks empty type/action looks empty the commit message "Update and rename patch_dev_release.py to patch_release.py": summary looks empty type/action looks empty the commit message "Update build_esptool.yml": summary looks empty type/action looks empty the commit message "Update build_esptool.yml": summary looks empty type/action looks empty the commit message "Update build_esptool.yml": summary looks empty type/action looks empty the commit message "Update build_esptool.yml": summary looks empty type/action looks empty the commit message "Update build_esptool.yml": summary looks empty type/action looks empty the commit message "Update build_esptool.yml": summary looks empty type/action looks empty the commit message "Update build_esptool.yml": summary looks empty type/action looks empty the commit message "Update build_esptool.yml": summary looks empty type/action looks empty the commit message "Update build_esptool.yml": summary looks empty type/action looks empty the commit message "Update build_esptool.yml": summary looks empty type/action looks empty the commit message "Update pack_python.py": summary looks empty type/action looks empty the commit message "Update package.json in repo when a release is done": summary looks empty type/action looks empty the commit message "Update package.json": summary looks empty type/action looks empty the commit message "Update patch_release.py": summary looks empty type/action looks empty the commit message "add esptool zip to release": summary looks empty type/action looks empty the commit message "comment for test": summary looks empty type/action looks empty the commit message "forgot rm hash": summary looks empty type/action looks empty the commit message "generate package.json": summary looks empty type/action looks empty the commit message "patch only in release case": summary looks empty type/action looks empty the commit message "rm elf map": summary looks empty type/action looks empty the commit message "rm hash": summary looks empty type/action looks empty the commit message "rm sha": summary looks empty type/action looks empty the commit message "s3 reset fix: align with upstream": summary looks empty type/action looks empty the commit message "set as release": summary looks empty type/action looks empty the commit message "simplify": summary looks empty type/action looks empty the commit message "updated files": summary looks empty type/action looks empty the commit message "updated files": summary looks empty type/action looks empty Please fix these commit messages - here are some basic tips: follow Conventional Commits style correct format of commit message should be: <type/action>(<scope/component>): <summary>, for example fix(esp32): Fixed startup timeout issue allowed types are: change,ci,docs,feat,fix,refactor,remove,revert,test sufficiently descriptive message summary should be between 20 to 72 characters and start with upper case letter avoid Jira references in commit messages (unavailable/irrelevant for our customers) TIP: Install pre-commit hooks and run this check when committing (uses the Conventional Precommit Linter).
⚠️	Please consider squashing your 50 commits (simplifying branch history).
⚠️	The **target branch** for this Pull Request **must be the default branch** of the project (`main_work`). If you would like to add this feature to a different branch, please state this in the PR description and we will consider it.

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

👋 Hello Jason2866, 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 via this public GitHub repository.

This GitHub project is public mirror of our internal git repository

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 synchronize it into our internal git repository.
4. In the internal git repository 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.
5. If the change is approved and passes the tests it is merged into the default branch.
5. On next sync from the internal git repository merged change will appear in this public GitHub repository.

Generated by 🚫 dangerJS against 306a330