Device trigger - sync value with initialHaFormData

[karwosts]

Proposed change

When computeInitialHaFormData sets up the form for the first time in device triggers, we need to actually push those selections to the value as well, or else the trigger can be broken. Consider this trigger:

computeInitialHaFormData sees the trigger contains a required select selector with 1 item, and defaults to selecting the first item. But until user interacts with the form there is no actual zone key published to the trigger value. Since it is already selected, clicking it again does nothing. Therefore this trigger is broken and there's no way to make the visual editor accept this trigger (without dropping into yaml mode), as seen by the error that there is a required zone, but it is already selected.

I might have thought we needed something similar for device conditions or device actions, but those don't use computeInitialHaFormData 🤷

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

[piitaya]

The device trigger is the only automation block using computeInitialHaFormData. Not sure why...

[farmio]

Maybe because I didn't think of the others (since I never implemented them 😬). See #20555