[New Data Source]: Aruba Central

### Background Problem / Motivation Aruba Central provides a high‑volume streaming telemetry interface for network and device analytics. The data is published in binary Protobuf format, which requires .proto schemas to decode. Grafana currently does not have a datasource capable of: - Connecting to Aruba Central’s streaming endpoint - Accepting user‑uploaded Protobuf schema files - Decoding the incoming Protobuf messages - Mapping fields to Prometheus metrics or Loki log entries - Optionally pushing decoded data to Grafana Cloud storage backends This limits the ability to monitor Aruba networks directly in Grafana without building custom middleware. ### Use case Aruba Central is widely adopted for enterprise network management. Native telemetry ingestion would: - Eliminate the need for custom ingestion services - Improve visibility into Aruba access points, switches, and gateways - Enable correlation with existing metrics/logs in Grafana Cloud - Expand Grafana’s footprint into the network observability space Requested Functionality 1. Datasource Type - A streaming‑capable Grafana datasource plugin that can connect to Aruba Central’s streaming platform using the documented API. 2. Connection Requirements - Support for Aruba Central Streaming API authentication - Ability to configure endpoint URLs, credentials, and topics/feeds 3. Protobuf Schema Support - Allow users to upload one or more .proto files - Plugin automatically compiles the schema internally - Use the schema to decode all incoming binary messages 4. Decoding & Mapping Decoded Protobuf messages should be mappable to: Prometheus Metrics - Numeric fields → metrics - Optional labels derived from string fields - User-defined metric naming conventions Loki Logs - Entire decoded message stored as structured JSON - Selectable fields exposed as labels for querying 5. Storage Target Options The datasource should provide a configuration option to route decoded output to: - Grafana Cloud Prometheus - Grafana Cloud L…