Configure generated NetRID flight data

[vgrafe]

Summary

• add num_flights and duration knobs to adjacent circular NetRID flight generation
• add a generated Kentland flight-data resource with 10 flights and 61 seconds of telemetry
• point the dev NetRID v19/v22a configs at generated Kentland data instead of the fixed Kentland KML fixture

Motivation

Follow-up to #1535, fixes #1533. Adding one more fixed KML flight only handles the current 3-SP case; the next added SP would hit the same one-flight-per-SP limit. Generated flight data lets baselines choose a flight count and telemetry duration suitable for the configured participant set while preserving deterministic defaults.

Validation

• PYTHONPATH=../.. ../../.venv/bin/pytest resources/netrid/flight_data_resources_test.py
• validated configurations/dev/netrid_v19.yaml: 0 config errors
• validated configurations/dev/netrid_v22a.yaml: 0 config errors
• generated Kentland source check: 10 flights, 61 telemetry states each, 0 injected_flights_errors
• make format from schemas
• make lint from schemas
• make lint from repo root