Configure generated NetRID flight data

[vgrafe]

Summary

• add num_flights and duration knobs to adjacent circular NetRID flight generation
• preserve the existing default behavior of 6 generated flights with 30 telemetry samples each
• add tests for default generation, configured generation, and invalid count/duration values
• regenerate the AdjacentCircularFlightsSimulatorConfiguration JSON schema

Motivation

Follow-up to #1533, scoped to reusable model support only. Project-specific NetRID baseline data/config changes belong in downstream project configuration, but monitoring can still expose the simulator controls needed by those downstream configurations.

Validation

• PYTHONPATH=../.. ../../.venv/bin/pytest resources/netrid/flight_data_resources_test.py
• schemas lint attempted after the amend, but Docker was unavailable: failed to connect to the docker API at unix:///Users/vincent.grafe/.docker/run/docker.sock

[BenjaminPelletier]

This PR seems good, but the Draft status communicates it's not ready for review yet -- were you planning to add or adjust anything else?

Validation

• PYTHONPATH=../.. ../../.venv/bin/pytest resources/netrid/flight_data_resources_test.py
• schemas lint attempted after the amend, but Docker was unavailable: failed to connect to the docker API at unix:///Users/vincent.grafe/.docker/run/docker.sock

Currently, docker is a critical tool for almost everything in this repository; I would highly recommend making sure it's installed, working, and available to any AI agent that may be assisting. I believe podman can be used instead of the tool available from Docker if needed.