Add LaserDetection message for tracked laser output

[jp-pino]

This pull request extends the protobuf message definitions to support new computer vision features related to laser detection, specifically for the Ultra model. It introduces new messages for representing 2D points and laser detection results, and updates telemetry to include detection data.

Additions for laser detection and telemetry:

• protobuf_definitions/message_formats.proto:
  • Added the modulated boolean field to the Laser message to indicate if the laser is modulated at 5Hz for tracking.
  • Introduced the Point2D message for representing 2D coordinates.
  • Added the LaserDetection message to encapsulate detected laser dot centroids, their pixel distance, detection confidence, and source image dimensions, supporting new computer vision features.

Telemetry enhancements:

• protobuf_definitions/telemetry.proto:
  • Updated the LaserTel message to include a laser_detection field, reporting computer vision-based laser detection status and details.

[Copilot]

Pull request overview

This PR extends the public protobuf schema to support Ultra-specific computer-vision laser tracking by adding a laser modulation flag, introducing new 2D/detection message types, and exposing detection results via telemetry.

Changes:

• Added modulated to Laser to indicate 5 Hz modulation for CV tracking (Ultra-only).
• Introduced Point2D and LaserDetection messages to represent detected dot centroids and related metadata.
• Extended LaserTel telemetry to include laser_detection.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
protobuf_definitions/message_formats.proto	Adds Laser.modulated plus new Point2D/LaserDetection message definitions for CV laser tracking.
protobuf_definitions/telemetry.proto	Adds LaserDetection to LaserTel telemetry to report CV laser detection results.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[follesoe]

One thing to consider (not sure if we need it or not) is if we should return the width of the laser in the telemetry, so that the messages are cohesive in themself? If not, consumer of the telemetry/log data needs to check the device ID of the connected laser, and then maintain a look up table with the device id <-> laser width.

This might be nice to have in libblunux, and expose. The draw back, is that this is static data so wastefull to include in every telemetry message.

🤔