feat(hosted): Add OTA and version functionality to esp-hosted

[me-no-dev]

This pull request adds firmware version management and update capabilities to the ESP-Hosted integration. The changes introduce functions for retrieving firmware versions, checking for updates, and managing over-the-air (OTA) updates of the co-processor. Additionally, the initialization process now checks for version mismatches and logs update information.

Firmware version management and update features:

• Added hostedGetHostVersion and hostedGetSlaveVersion functions to retrieve the firmware version of the host and co-processor, respectively. [1] [2]
• Implemented hostedHasUpdate to compare host and slave firmware versions, log differences, and determine if an update is needed. [1] [2]
• Added hostedGetUpdateURL to generate a URL for downloading the appropriate firmware update. [1] [2]

OTA update workflow:

• Introduced hostedBeginUpdate, hostedWriteUpdate, and hostedEndUpdate for starting, writing, and finalizing OTA updates to the co-processor. [1] [2]

Initialization improvements:

• Modified hostedInit to connect to the slave device and automatically check for firmware updates during initialization, logging results as appropriate.

Code cleanup:

• Updated includes and removed redundant external declarations for initialization functions.

[github-actions]

	Messages
📖	🎉 Good Job! All checks are passing!

👋 Hello me-no-dev, 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 99e010c

[github-actions]

Test Results

0 tests   0 ✅  0s ⏱️
0 suites  0 💤
0 files    0 ❌

Results for commit 99e010c.

♻️ This comment has been updated with latest results.