chore: scope CI, E2E, Docs, and Release workflow triggers

[tukuyomil032]

Summary

• Scope CI and E2E workflow triggers to application, test, build, and Playwright inputs.
• Scope Docs deployment to Astro/Starlight sources, TypeDoc inputs, and workspace dependency metadata.
• Prevent Release builds and publishing when authoritative application metadata did not change version.
• Keep the scheduled and manually dispatched Minecraft version updater unchanged.

Workflow changes

• ci.yml: add an application/build/test allowlist for push events.
• e2e.yml: use the same Playwright-relevant allowlist for pull requests and pushes to main; unit-test-only changes do not start E2E.
• docs.yml: remove broad application source triggers and watch only docs sources plus the three TypeDoc entry-point areas (src/lib, src/store, and src/renderer/components).
• release.yml: watch only release metadata and validate the package/Tauri/Cargo versions before release. Unchanged versions skip release work.
• update-versions.yml: intentionally unchanged because its schedule and manual dispatch are independent of changed paths.

Validation

• pnpm check
• pnpm lint
• pnpm test (318 passed)
• pnpm typecheck:tests
• pnpm build
• pnpm --filter @mc-vector/docs build:full
• cargo test --manifest-path src-tauri/Cargo.toml (52 passed, 1 ignored)
• pnpm exec tauri build --debug --no-bundle
• pnpm e2e (50 passed)
• actionlint on all changed workflows

The pushed CI run is green across lint, cargo-audit, and macOS/Windows build checks: https://github.com/tukuyomil032/MC-Vector/actions/runs/33749538086