feat!: migrate edge & proxy to new builder

[Nerivec]

• Use HA-provided builder workflow with small modifications to better fit use cases
• Rewrite to use s6-overlay & co, and improve configuration handling
• ⚠️ BREAKING: Use addon_config mapping.
  • Config folder is now included in Home Assistant add-on backups
  • Each add-on now has its own config folder (if wanting to switch between regular and edge add-ons, you must copy over the data)
  • The toggle to delete the add-on data when uninstalling the add-on will now remove your Zigbee2MQTT configuration (yaml, db, logs, etc.)
• All configuration.yaml settings are now handled either through the onboarding (can be forced in add-on configuration tab), the frontend once Zigbee2MQTT has started, or directly in the file itself (using add-on while Zigbee2MQTT is stopped)
• The Zigbee2MQTT watchdog is now enabled by default, with default settings
• [ADVANCED] For easier debugging, can now override app code through app_overrides folder in add-on config folder
  • On add-on start, if the app_overrides folder exists, its content is copied over the Zigbee2MQTT app folder (using exact folder structure)
  • Deleting the app_overrides folder will remove any override on next add-on start

See Nerivec/ha-zigbee2mqtt#2 for previous auto-migration testing details.

See https://github.com/Nerivec/zigbee2mqtt-windfront/blob/5fd113b61b0ce34ad0dce355c38cfd43c049dc51/.github/workflows/ci.yml#L138-L147 for example use of the manual-builder workflow (example run)

See https://github.com/Nerivec/zigbee2mqtt-windfront/blob/5fd113b61b0ce34ad0dce355c38cfd43c049dc51/.github/workflows/ci.yml#L149-L158 for example use of the bump-version workflow (example result PR)

See https://github.com/Nerivec/ha-zigbee2mqtt-windfront/actions/runs/19746873199 for example run of builder workflow (from merging PR created by above workflow - auto detect changes).

---

This does not migrate the "regular" add-on, will be done separately (dedicated folder, common folder & workflows remain the same).

[Koenkk]

Each add-on now has its own config folder (if wanting to switch between regular and edge add-ons, you must copy over the data)

Can this be done automatically somehow? Because this makes it quite hard for people to switch.

[Nerivec]

Err, misread, first reply deleted.
I don't think so, this would count as cross-over, add-on security won't allow that. Might be able to work around it, but would have to lower security a lot to allow it (mounting stuff we should not be mounting & co), add-on quality score would get smashed. Have to double check though, I did this stuff a while back. 😅 Maybe the HA guys know of a way to do this.

We'd also hit the problem of "copy the data over or not?", since now the two add-ons could run simultaneously and one could have edge running for a specific purpose, and regular for another, without wanting to copy data across.

[github-actions]

This pull request is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days

[github-actions]

This pull request is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days