Fix BLE notification properties and add missing ESC telemetry notifications

[Copilot]

The BLE implementation had inconsistencies between characteristic property declarations and actual notification behavior. ESC telemetry wasn't notifying clients of updates, and several BMS characteristics called notify() without declaring the NOTIFY property.

Fixed ESC Service Notifications:

• Added NIMBLE_PROPERTY::NOTIFY to all ESC characteristics (voltage, current, RPM, temperatures)
• Added notify() calls in updateESCTelemetryBLE() with connection check
• Added ESC_TELEMETRY_SERVICE_UUID to BLE advertising

Fixed BMS Service Property Declarations:

• Added NIMBLE_PROPERTY::NOTIFY to telemetry characteristics that were already calling notify() (SOC, voltage, current, power, cell voltages, temperatures, voltage differential)

Before:

pESCVoltage = pEscService->createCharacteristic(
    NimBLEUUID(ESC_VOLTAGE_UUID), NIMBLE_PROPERTY::READ);
// updateESCTelemetryBLE() had no notify() calls

After:

pESCVoltage = pEscService->createCharacteristic(
    NimBLEUUID(ESC_VOLTAGE_UUID), NIMBLE_PROPERTY::READ | NIMBLE_PROPERTY::NOTIFY);

// In updateESCTelemetryBLE():
if (!deviceConnected) return;
if (pESCVoltage) pESCVoltage->notify();

All BLE characteristics now properly declare NOTIFY when sending notifications, ensuring correct BLE protocol compliance and real-time telemetry updates.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.