fix(frontend): drop dead resample trigger/resolutions config

config.ResampleConfig stopped emitting the trigger and resolutions fields,
but MetricPlot still read them. resampleResolutions and resampleMinimum
were therefore always null, which made the array-based resolution branch in
the setScale hook unreachable and the timestep !== resampleMinimum guard
always true. Keep only the policy-based branch and derive the zoom trigger
straight from targetPoints.

configs/config-large.json still carried the removed minimum-points, trigger
and resolutions keys, which DisallowUnknownFields now rejects, so starting
against it aborted. Replace them with the current keys and add a test that
loads the file, so the example configs cannot drift out of the schema
unnoticed again.

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

configs/config-large.json

@@ -4,9 +4,8 @@
     "short-running-jobs-duration": 300,
     "emission-constant": 317,
     "resampling": {
-      "minimum-points": 600,
-      "trigger": 30,
-      "resolutions": [600, 300, 120, 60]
+      "default-policy": "medium",
+      "default-algo": "average"
     },
     "api-subjects": {
       "subject-job-event": "cc.job.event",