Add hosted demo page to showcase the integration (map, sensors, calendar animation)

[Pascal-ZeGerman]

Create a hosted demo page so users can try the GPS2ASP-Resolver integration without installing Home Assistant. The demo should let someone place a location on a map, see the parking restrictions for a given car, observe the "next move" calculation, and view sample Home Assistant sensor outputs. The demo must also include a small calendar mock-up that animates the computed next-move date.

Requirements / goals

• Hosting
  • Preferred: GitHub Pages (static site in this repo or a docs/ site). Alternative: run on user's homelab (less preferred).
  • The demo must be runnable without a full HA install.
• Lightweight demo mode
  • A sped-down resolver mode that only supports a set of pre-defined locations and/or a simplified rule set so the demo is fast and deterministic.
  • Must run entirely client-side or with a tiny server (static JSON + client JS preferred) so it is easy to host on GitHub Pages.
• Map interaction
  • User can place a pin (or click) on a map and the demo will resolve the chosen location against the demo resolver.
  • Map should show the pin, and highlight the matched demo location/zone when applicable.
  • Suggested UI: Leaflet + OpenStreetMap tiles.
• Parking restrictions + Next-move
  • Display the resolved parking restriction for the selected location (text + human-friendly summary).
  • Show the "next move" date/time calculation for the currently selected car/profile.
  • Provide a small UI to pick a sample car/profile (e.g., car A/B with different plates or rules) to demonstrate how results vary.
• Home Assistant sensors preview
  • Show sample HA sensor outputs as they would appear in Home Assistant (entity_id, state, attributes). A read-only mock card or side panel is fine.
  • Provide example JSON snippets that can be copy-pasted into HA for testing.
• Calendar animation
  • Include a compact calendar mock-up that animates/highlights the computed "next move" date (for example: fade-in or slide the date into view, highlight day cell, show tooltip with reason).
• Accessibility & UX
  • Make the demo usable on desktop and tablet widths. Keep UI simple and clear.

Acceptance criteria

• Hosted demo URL (GitHub Pages or sample homelab instructions) or clear instructions to enable demo locally.
• A static dir or docs/ site in the repo containing the demo sources and build steps (if any).
• A functioning map where the user can select a location and see resolved parking restrictions from the demo dataset.
• A visible mock of Home Assistant sensors showing the current output for the selected location/profile.
• Calendar mock with animation showing the computed next-move date.
• README.md updates with how the demo works, where data comes from, and how to run/host it.

Implementation notes / suggestions

• Use Leaflet + OSM for map and interactivity; bundle a small set of demo zones as GeoJSON in the repo (e.g., 5–10 representative NYC addresses/segments).
• Implement the demo resolver in pure JS (reusing Python logic via a precomputed JSON dataset or a tiny Python HTTP endpoint if necessary). Aim for client-side first so GitHub Pages hosting works.
• Provide a toggle to run the "full resolver" mode (if backend is available) vs the "demo mode" (predefined dataset) so maintainers can demonstrate both.
• Include a minimal mock Home Assistant card UI showing sensor entity_id, state, and attributes; show a Paste-to-HA block with example YAML/JSON for users who want to replicate the sensors.
• Keep the demo small and dependency-light so it can be hosted under GitHub Pages or included in the project's docs site.

Notes for maintainers

• Label the branch/docs as demo/ or docs/demo/ and consider enabling GitHub Pages from docs/.
• If a backend is required, prefer a tiny serverless or static JSON approach to keep hosting simple.

If implemented, this will make it trivial for users to understand what the integration does and lower the barrier for adoption and testing.