ci(release): Add package JSON with chinese mirrors

[lucasssvaz]

Description of Change

This pull request enhances the release script (.github/scripts/on-release.sh) to support generating and handling package JSON files for a Chinese mirror (dl.espressif.cn). The changes ensure compatibility with the Chinese mirror by adding new JSON files, modifying commands, and updating upload logic.

Support for Chinese mirror:

• Added new variables PACKAGE_JSON_DEV_CN and PACKAGE_JSON_REL_CN to handle Chinese mirror-specific package JSON files.
• Updated the sed command to replace URLs for the Chinese mirror (github.com → dl.espressif.cn/github_assets) while generating the Chinese-specific JSON files.
• Modified the merge_package_json logic to include merging of Chinese mirror-specific JSON files during release preparation.
• Added a note that package JSONs for the Chinese mirror are not tested during the release process, as the mirror might not yet be updated.
• Enhanced the upload steps to include uploading the Chinese mirror-specific JSON files to both GitHub assets and GitHub Pages.

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

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

---

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

---

🖊️ Please also make sure you have read and signed the Contributor License Agreement for this project.

---

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 1dad781