Add drone-rid-observation MISP object template

[adulau]

Motivation

• Provide a concise MISP object to encode direct Remote ID (RID) broadcasts for drones/UAS that covers common US (ASTM/FAA) and EU (EN/Regulatory) use-cases.
• Support practical observation, triage and correlation without embedding full protocol details, while leaving room for DRIP/identity-assurance hints.

Description

• Add a new object file objects/drone-rid-observation/definition.json containing telemetry, identity, operational and collection fields for RID observations.
• Key attributes include observation-time, uas-id, operator-id, session-id, latitude, longitude, altitude-m, speed-mps, heading-deg, rid-standard-profile, broadcast-tech, auth-claim, raw-message, receiver-id, confidence, and comment.
• Validation constraints require observation-time and at least one of uas-id / operator-id / session-id via requiredOneOf.
• File includes a stable uuid and version and uses existing MISP attribute types (e.g., float, text, datetime).

Testing

• Ran a JSON sanity check with jq . objects/drone-rid-observation/definition.json which completed successfully.
• Ran ./jq_all_the_things.sh which completed and reformatted files but emitted environment warnings (uuidparse: command not found).
• ./validate_all.sh previously exited non-zero due to the repository validation rule that enforces a clean diff when adding new objects, so that check failed as expected in this workflow.

---

Codex Task