Add ADS-B and AIS observation objects; update AIS metadata and versions

[adulau]

Motivation

• Provide structured telemetry observation objects for aviation and maritime sensors to capture ADS-B and AIS security anomalies (spoofing, replay, jamming, etc.).
• Clarify AIS metadata semantics and separate baseline AIS telemetry from security-focused observations.
• Bump object versions to reflect non‑backward changes to ais and ais-info definitions.

Description

• Added objects/ads-b-observation/definition.json defining an ads-b-observation object with attributes such as icao24, callsign, latitude, longitude, barometric-altitude-ft, geometric-altitude-ft, attack-type, detection-method, suspicion-score, timestamps, and other telemetry fields. The object uses icao24 as a required identifier and includes a new UUID and version: 1.
• Added objects/ais-observation/definition.json defining an ais-observation object with attributes such as MMSI, IMO-number, name, latitude, longitude, speed-over-ground, attack-type, detection-method, suspicion-score, raw-message, observation-type, and related context fields, with required identifiers and a new UUID at version: 2.
• Updated objects/ais-info/definition.json to expand the description to clarify that ais-info documents sharing provenance/context (not maritime AIS protocol fields) and bumped version to 2.
• Updated objects/ais/definition.json to clarify the description that ais is baseline vessel telemetry (to be used with ais-observation) and bumped version to 4.

Testing

• Ran JSON schema validation and object linting (jsonschema/repo linters) against the modified object definitions and they passed.
• No unit tests were added in this change set and existing test suites targeting objects completed without failures.

---

Codex Task