- Add test_framework_integration.js with 32 tests covering:
  - Framework core validation (main.js, app-controller, services)
  - App structure compliance (example and jira apps)
  - Throwaway app creation test (validates framework contract)
  - Version compatibility matrix across all apps
  - Security configuration validation (nodeIntegration, contextIsolation)

- Update workflow to run framework integration tests

The throwaway app test is the key TDD test:
- Creates a minimal app using the same pattern as documented apps
- Uses the same Electron version that Dependabot would update
- Verifies the framework contract is not broken by updates

Total: 84 tests across 5 test files

Renamed for clarity:
- test_jira_app.js -> test_electron_jira_app.js
- test_example_app.js -> test_electron_example_app.js
- test_emr_dashboard.js -> test_electron_emr_dashboard.js
- test_functional.js -> test_electron_functional.js
- test_framework_integration.js -> test_electron_framework_integration.js

Updated workflow references to match new filenames.

Dependabot config changes:
- Enable PRs for Example app (was monitor-only, now limit: 1)
- Enable PRs for Jira app (was monitor-only, now limit: 1)
- All Electron apps now on weekly schedule (Monday)
- Added 'electron' label to all Electron app configs

Test changes:
- Throwaway app test now uses FRAMEWORK electron version
  (src/gaia/electron/package.json) as the canonical source
- This ensures the test validates against what Dependabot updates

Now Dependabot will update:
- Root package.json (npm workspaces master)
- src/gaia/electron (framework)
- src/gaia/apps/example/webui
- src/gaia/apps/jira/webui
- src/gaia/agents/emr/dashboard/electron

Review feedback addressed:

1. Unused imports (test_electron_framework_integration.js)
   - Removed unused `execSync` and `spawn` from imports

2. Hardcoded version requirements
   - Extracted MIN_ELECTRON_VERSION (31) and MIN_FORGE_VERSION (7) as constants
   - Added detailed documentation explaining why these versions are required
   - Constants are now in one place for easy maintenance

3. Hardcoded 5-second timeout
   - Made configurable via ELECTRON_LAUNCH_TIMEOUT_MS environment variable
   - Added documentation explaining why 5 seconds is the default
   - Apps with heavy initialization can override if needed

4. Platform-specific packaging
   - Added comments clarifying this runs on Linux (ubuntu-latest)
   - Windows/macOS packaging is tested in separate workflow
   - Added DEBUG output for electron-forge troubleshooting

The apps (jira, example) are part of npm workspaces defined in root
package.json. Running 'npm ci' in the subdirectory doesn't work because
workspaces hoist dependencies to the root node_modules.

Fix: Install from root directory which properly installs all workspace
dependencies including electron.

electron-forge uses the local package-lock.json to determine project root
and expects electron to be installed there. With npm workspaces, dependencies
are hoisted to root but forge still looks locally.

Fix: Run npm install in app directory after root npm ci to ensure electron
is available where forge expects it.