Match the Driver Station's telemetry ordering and formatting

[mxtmx]

Telemetry now shows in the same order and format as on the Driver Station.

• Order: items appear in the order they were added instead of alphabetically, and addLine() puts its text in place instead of in the log below. Packets carry an ordered item list next to the keyed data, which the graph and logging views still read.
• Formatting: the client used to render every value as raw HTML, so a stray < broke the line and robot markup was an XSS risk. Packets now carry a display format. HTML renders the subset the Driver Station supports, safely, and CLASSIC and MONOSPACE show plain text. The Telemetry view has a menu to override the format, and ESLint now rejects dangerouslySetInnerHTML.
• Telemetry adapter: it now works like the SDK's TelemetryImpl. addData() returns an item, value producers are re-evaluated, retained items and setAutoClear work, Double and Float are rounded, captions and values are separated by " : ", and a repeated caption shows twice.
• Logging CSV: each log entry is exported once, using the new logRange numbering, and bare lines get their own column.
• MultipleTelemetry.removeItem() and removeLine() remove from every delegate.
• TelemetryPacket gains addItem() (with Item.appendValue()) and putData() for hand-built packets.

TelemetryPacketTests and DashboardTelemetryTests cover the new behaviour.

Breaking changes:

• TelemetryPacket.addLine() adds an in-place line instead of a log entry, and clearLines() clears only those lines. Use addLogEntry() for the log.
• FtcDashboard.getTelemetry() defaults to CLASSIC like the Driver Station, so markup needs setDisplayFormat(HTML). Hand-built packets still default to HTML. This is the most contentious change, since teams relying on HTML will see raw tags.
• MultipleTelemetry.addAction() runs an action once per loop instead of once per delegate, and MultipleItem.addData() returns the added item instead of itself, as in the SDK.

The new packet fields (items, displayFormat, captionValueSeparator, telemetryFrame, logRange) are optional, so older robots still work. Packets from the Telemetry adapter now carry the whole retained log each time.

format-menu-dark.mp4