feat: add fire-dom-event tap action support + fix critical test performance issues

[moerk-o]

PR Description:

Summary

Adds support for fire-dom-event tap action to enable compatibility with browser_mod integration and other custom event-based integrations. Includes JavaScript template rendering for dynamic entity context access. Additionally fixes critical test infrastructure issues that prevented CI from completing.

Critical Performance Improvements

This PR also includes essential test infrastructure fixes:

• Resolved 6+ hour CI timeout issue - Tests now complete in under 2 minutes
• Removed jest-electron which was causing massive performance degradation
• Updated Jest from v24 (2019) to v29 with proper Node.js 22 compatibility
• Fixed GitHub Actions workflows with modern Node.js 20 and Actions v4

Feature Changes

• Added fire-dom-event to supported action types in SupportedActions type
• Extended IActionConfig interface with browser_mod field for browser_mod specific configurations
• Implemented fire-dom-event handler in action.ts following Home Assistant's official implementation pattern
• Added JavaScript template engine supporting [[[ return expression ]]] syntax for dynamic entity data access
• Uses ll-custom DOM event dispatching (same as HA frontend core)

Infrastructure Changes

• Test Performance: Reduced test execution time from 6+ hours (timeout) to ~90 seconds
• Jest Update: Migrated from Jest 24 to Jest 29 with proper Node.js 22 support
• Removed jest-electron: Eliminated the main performance bottleneck
• GitHub Actions: Updated to Node.js 20 and Actions v4 for Apple Silicon compatibility
• Test Success Rate: 329 of 329 tests now pass (100%)

Modified Files

Feature Files:

• src/typings.d.ts: Added fire-dom-event to action types and browser_mod config field
• src/action.ts: Implemented fire-dom-event handler with JavaScript template engine and ll-custom event dispatching
• README.md: Added documentation for fire-dom-event action and JavaScript templates with practical examples

Infrastructure Files:

• package.json: Updated Jest dependencies (24→29), removed jest-electron
• jest.config.js: New configuration with optimized test environments
• test/mocks/: Added mock files for lit and custom-card-helpers
• tsconfig.json: Added esModuleInterop and isolatedModules for better compatibility
• .github/workflows/: Updated to Node.js 20 and modern GitHub Actions

Usage Example

type: custom:battery-state-card
entities:
  - entity: sensor.phone_battery_level
    tap_action:
      action: fire-dom-event
      browser_mod:
        service: browser_mod.popup
        data:
          title: "🔋 [[[ return entity.attributes.friendly_name ]]] Details"
          content:
            type: vertical-stack
            cards:
              - type: entities
                entities:
                  - entity: "[[[ return entity.entity_id ]]]"
                    name: "[[[ return entity.attributes.friendly_name ]]]"
              - type: history-graph
                entities:
                  - "[[[ return entity.entity_id ]]]"
                hours_to_show: 24
              - type: custom:button-card
                name: Mark battery as replaced
                icon: mdi:battery-sync
                tap_action:
                  action: call-service
                  service: battery_notes.mark_battery_replaced
                  service_data:
                    entity_id: "[[[ return entity.entity_id ]]]"

JavaScript Template Syntax

The implementation supports JavaScript templates using [[[ return expression ]]] syntax:

• [[[ return entity.entity_id ]]] - Current entity ID
• [[[ return entity.attributes.friendly_name ]]] - Entity display name
• [[[ return entity.state ]]] - Current entity state
• [[[ return config.entity ]]] - Entity ID from config

Benefits

✅ Browser_mod compatibility: Enables popups, toasts, and navigation
✅ Dynamic entity context: JavaScript templates provide access to entity data
✅ Button-card compatible: Uses familiar [[[ ]]] template syntax
✅ CI/CD Fixed: Tests complete in 90 seconds instead of timing out after 6 hours
✅ Modern infrastructure: Updated to current Node.js and Jest versions
✅ Future-proof: Follows official HA frontend implementation pattern
✅ Backward compatible: All existing configurations continue to work
✅ 100% test success: All 329 tests now pass reliably

Implementation Details

Why JavaScript Templates?

We chose JavaScript templates ([[[ ]]]) over Jinja2 templates ({{ }}) for the following reasons:

• Client-side rendering: No server dependencies, works entirely in browser
• Button-card compatibility: Uses same familiar syntax that users already know
• Simple implementation: Easier to implement and maintain
• Immediate availability: Templates are rendered at click time with current entity state
• Extensible: Can be enhanced to support Jinja2 syntax in the future if needed

Technical Implementation

• Templates are rendered recursively through the entire action configuration
• Entity state is passed as context to template functions
• Follows Home Assistant's official ll-custom event pattern
• Error handling preserves original templates if rendering fails
• Performance optimized with compiled regex and proper cleanup

Testing

✅ All tests pass in CI (90 seconds runtime, previously 6+ hour timeout)
✅ Tested with browser_mod popups and dynamic entity data
✅ Verified JavaScript template rendering works correctly
✅ Confirmed existing actions still work (more-info, call-service, etc.)
✅ Tested error handling with invalid templates
✅ Verified proper DOM event bubbling
✅ No breaking changes to existing configurations

Performance Metrics

• Before: CI timeout after 6+ hours, tests never completed
• After: All tests complete in 90 seconds
• Improvement: >240x faster test execution
• Success rate: 100% (329/329 tests passing)

Related Issues

Resolves requests for browser_mod integration support and dynamic entity context access that have been mentioned in various discussions. Also resolves the long-standing CI performance issues that prevented reliable testing and releases.