Migrate final TypeScript to HTML (#14)

* Reduce JavaScript on firmware install pages

- Created new install.html layout for firmware install pages
- Converted all install pages to use static Nunjucks layout instead of TypeScript/Lit components
- Eliminated need for page-specific TypeScript files (vpe-install.ts, zbt1-install.ts, zwa2-install-portable.ts, zwa2-install-poe.ts)
- Pages now use declarative front matter configuration instead of imperative JavaScript
- Maintains all existing functionality with significantly less JavaScript overhead
- Updated pages: ZWA-2 install, ZWA-2 portable, ZWA-2 PoE, ZBT-1 install, VPE install

This change reduces the amount of JavaScript loaded on firmware installation pages while keeping the same visual appearance and functionality.

* Simplify ZWA-2 install pages to static HTML

- Simplified install.html layout to only provide CSS and back navigation
- Removed backLabel frontmatter variable (always uses "Back")
- Converted ZWA-2 install pages to pure static HTML:
  - Removed frontmatter variables: installerElement, installerScript, installerAttributes
  - Script tags and installer elements now directly in page HTML
  - Troubleshooting sections included directly as static HTML
- Pages are now completely declarative with no dynamic templating
- URLs remain unchanged (still use /install/, /install-portable/, /use-poe/)

This significantly reduces JavaScript and makes pages easier to maintain as plain HTML.

* Fix install layout to use safe filter for content rendering

* Tweaks

* Clean up unused deps

* Permanlinks not needed

* Remove linting

---------

Co-authored-by: Claude <[email protected]>

Author: balloob

.github/workflows/deploy.yml

@@ -2,9 +2,9 @@ name: Deploy to GitHub Pages
 
 on:
   push:
-    branches: [ main ]
+    branches: [main]
   pull_request:
-    branches: [ main ]
+    branches: [main]
 
 # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
 permissions:
@@ -15,7 +15,7 @@ permissions:
 # Allow only one concurrent deployment, skipping runs queued between the run in-progress and latest queued.
 # However, do NOT cancel in-progress runs as we want to allow these production deployments to complete.
 concurrency:
-  group: "pages"
+  group: 'pages'
   cancel-in-progress: false
 
 jobs:
@@ -35,9 +35,6 @@ jobs:
       - name: Install dependencies
         run: npm ci
 
-      - name: Lint
-        run: npm run lint
-
       - name: Build
         run: npm run build
         env: