Deploy the example to GitHub Pages

[SantaClaas]

Publishes the example to https://santaclaas.github.io/material-tailwind/ on
every push to main, so the plugin's output can be seen without checking out
and building the repository. Pages is already set to the "GitHub Actions"
source, so this workflow is what deploys.

Build and deploy are separate jobs, as in the release workflow, so build-time
dependencies never hold the token that can publish.

Installing takes two steps because the example is its own pnpm workspace that
links to the repository root: the root install provides the plugin's own
dependencies, which the link cannot pull in on its own. The example install
keeps build scripts enabled, unlike the other workflows, because esbuild has to
unpack its binary; pnpm still only runs what the allowBuilds list permits.

Vite gets base: "./" so the built asset URLs are relative and resolve under
the /material-tailwind/ subdirectory a project site is served from. A relative
base rather than the hardcoded path keeps the dev server at /.

Verification

• Built from a clean checkout with no node_modules using the exact workflow
  commands.
• Served the output from a /material-tailwind/ subpath and loaded it in a
  browser: renders correctly, all assets 200, no console errors.
• zizmor reports no findings across all four workflows.

🤖 Generated with Claude Code