fix(deploy): make helper deployment reliable and isolated

[Auda29]

What changed

• create Home Assistant helpers with the generated ST entity ID, then restore the human-readable name via the update API
• verify the ID returned by Home Assistant and clean up partial creations on mismatch or rename failure
• scope helper discovery and deletion to the program currently being deployed
• add unit coverage plus a hard E2E deployment with a {persistent} variable
• assert that a helper belonging to another ST program remains untouched
• rebuild the committed HACS frontend bundle

Root cause

Home Assistant derives a storage helper's immutable ID from the name supplied at creation. The deploy path sent only the friendly name, so the generated helper could never match the entity ID expected by transpilation and verification. In addition, helper sync loaded every st_* helper on the instance, so deploying one program could delete helpers owned by another.

Impact

Programs using {persistent}, {throttle}, or generated timer helpers can now create the expected entities instead of failing verification and rolling back. Helper cleanup no longer targets other deployed programs.

Validation

• 226/226 frontend unit tests
• TypeScript typecheck
• ESLint: 0 errors (71 existing warnings)
• production bundle build and committed-bundle drift check
• GitHub Actions E2E is the merge gate; no local Docker/HA test was run, per request