feat(playwright): enable Playwright in production builds with custom browser path

Move Playwright from dev to production dependencies and implement robust browser
management for company deployment environment:

- Move playwright and playwright-core to dependencies
- Set PLAYWRIGHT_BROWSERS_PATH to user data directory before imports
- Add startup validation for Chromium browser with friendly error dialog
- Update build scripts to skip browser download during build process
- Configure electron-builder to unpack Playwright for native module access
- Add deployment documentation for browser setup in restricted environments

This allows manual browser installation in company environments where direct
downloads are blocked during build.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

electron-builder.yml

@@ -10,11 +10,17 @@ files:
   - '!{.env,.env.*,.npmrc,pnpm-lock.yaml}'
   - '!{tsconfig.json,tsconfig.node.json,tsconfig.web.json}'
   - 'package.json'
+  # Include build output
+  - 'out/**/*'
   # Include config.template.yaml in the build for reference
   - 'config.template.yaml'
+  # Exclude Playwright browser downloads (manual install for company environment)
+  - '!**/node_modules/playwright-core/.local-browsers/**'
 asarUnpack:
   - resources/**
+  # Unpack playwright for native modules
   - '**/node_modules/playwright/**'
+  - '**/node_modules/playwright-core/**'
 win:
   executableName: erpauto
   target: