ci(haos): cross-trigger both lanes on either workflow change

Both HAOS lanes now share the same qcow2 cache key, so any change to
the cache logic in one workflow needs to be verified in the other.
Add each workflow's path to the other's pull_request paths filter so
a single-file edit triggers both lanes.

Without this, a PR that only edits haos-e2e-inaddon-tests.yml
(like this one's first commit) would leave the external lane dormant
on CI, hiding any parity regression until a later PR happened to
touch a path both lanes already filter on.

Author: kingpanther13

.github/workflows/haos-e2e-inaddon-tests.yml

@@ -27,6 +27,10 @@ on:
       - 'homeassistant-addon/**'
       - 'homeassistant-addon-dev/**'
       - '.github/workflows/haos-e2e-inaddon-tests.yml'
+      # Trigger on external workflow changes too — both lanes share the
+      # qcow2 cache key, so a change to either workflow's cache logic
+      # needs the other lane to re-run for parity verification.
+      - '.github/workflows/haos-e2e-tests.yml'
   workflow_dispatch:
     inputs:
       pytest_args:

.github/workflows/haos-e2e-tests.yml

@@ -20,6 +20,10 @@ on:
       - 'pyproject.toml'
       - 'homeassistant-addon/**'
       - '.github/workflows/haos-e2e-tests.yml'
+      # Trigger on inaddon workflow changes too — both lanes share the
+      # qcow2 cache key, so a change to either workflow's cache logic
+      # needs the other lane to re-run for parity verification.
+      - '.github/workflows/haos-e2e-inaddon-tests.yml'
   workflow_dispatch:
     inputs:
       pytest_args: