Flatten to a single package directory

The checkout is now astrape/astrape-oracle, not astrape/astrape-oracle/<package>. The package
contents move to the repository root and pyproject maps the package name to
'.' via package-dir, with the subpackages listed explicitly.

The systemd units move out to /srv/astrape/deploy/systemd, outside every
repository, because they describe this deployment rather than any one
component.

Verified both install modes: editable, which is how the deployment runs, and
a plain wheel install, which is what the container build does.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

classes/datasets.py

@@ -0,0 +1,28 @@
+"""Shapes the stores return for display.
+
+These live beside the stores rather than beside the renderers on purpose. A
+store's return type belongs to the store: putting them in the dashboard would
+mean astrape-oracle importing astrape-dashboard, which is backwards -- the
+dashboard reads from the oracle, never the other way round.
+"""
+
+from __future__ import annotations
+
+from dataclasses import dataclass
+
+from gibil.classes.models import (
+    WeatherForecastPoint,
+    WeatherResolvedTruth,
+    WeatherStationObservation,
+)
+
+
+@dataclass(frozen=True)
+class WeatherDisplayDataset:
+    forecast_points: list[WeatherForecastPoint]
+    resolved_truth: list[WeatherResolvedTruth]
+
+
+@dataclass(frozen=True)
+class WeatherStationDisplayDataset:
+    observations: list[WeatherStationObservation]