Implement handling for BLE advType = 0x0c

**Describe the problem you have/What new integration you would like**
Possibility to handle advertisements and data from medial sensors such as blood pressure or oxygen measurements.

**Please describe your use case for this integration and alternatives you've tried:**
I have tried to configure the sensors for handling but ESPHome have not integrated any handling of advertisement type 0x0c

**Additional context**
I am trialing this with the FSRKB_BT-002 sensor which is used by multiple ble enabled bloodpressure meters. I have captured the following data but are unable (afaik) to process this further as no event seems to be triggering on unhandled types.

[12:36:14][V][esp32_ble_tracker:702]: Unhandled type: advType: 0x0c
[12:36:14][VV][esp32_ble_tracker:505]: Parse Result:
[12:36:14][VV][esp32_ble_tracker:522]: Address: 65:56:02:04:05:75 (PUBLIC)
[12:36:14][VV][esp32_ble_tracker:524]: RSSI: -76
[12:36:14][VV][esp32_ble_tracker:525]: Name: 'FSRKB_BT-002'
[12:36:14][VV][esp32_ble_tracker:527]: TX Power: 2
[12:36:14][VV][esp32_ble_tracker:533]: Ad Flag: 6
[12:36:14][VV][esp32_ble_tracker:536]: Service UUID: 0xFFE0
[12:36:14][VV][esp32_ble_tracker:555]: Adv data: 02.01.06.03.02.E0.FF.0D.09.46.53.52.4B.42.5F.42.54.2D.30.30.32.02.0A.00.05.0C.50.00.50.00 (30)

[12:36:15][V][esp32_ble_tracker:702]: Unhandled type: advType: 0x0c
[12:36:15][VV][esp32_ble_tracker:505]: Parse Result:
[12:36:15][VV][esp32_ble_tracker:522]: Address: 65:56:02:04:05:75 (PUBLIC)
[12:36:15][VV][esp32_ble_tracker:524]: RSSI: -76
[12:36:15][VV][esp32_ble_tracker:525]: Name: 'FSRKB_BT-002'
[12:36:15][VV][esp32_ble_tracker:527]: TX Power: 2
[12:36:15][VV][esp32_ble_tracker:533]: Ad Flag: 6
[12:36:21][VV][esp32_ble_tracker:536]: Service UUID: 0xFFE0

[12:36:28][V][esp32_ble_tracker:702]: Unhandled type: advType: 0x0c
[12:36:28][VV][esp32_ble_tracker:505]: Parse Result:
[12:36:28][VV][esp32_ble_tracker:522]: Address: 65:56:02:04:05:75 (PUBLIC)
[12:36:28][VV][esp32_ble_tracker:524]: RSSI: -66
[12:36:28][VV][esp32_ble_tracker:525]: Name: 'FSRKB_BT-002'
[12:36:28][VV][esp32_ble_tracker:527]: TX Power: 2
[12:36:28][VV][esp32_ble_tracker:533]: Ad Flag: 6
[12:36:28][VV][esp32_ble_tracker:536]: Service UUID: 0xFFE0
[12:36:28][VV][esp32_ble_tracker:551]: UUID: 0xFE9F
[12:36:28][VV][esp32_ble_tracker:552]: Data: 00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00 (20)
[12:36:28][VV][esp32_ble_tracker:555]: Adv data: 03.03.9F.FE.17.16.9F.FE.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.09.FF.E0.00.64.37.CA.74.B1.1A (38)

Start in the ESP32 BLE tracker handling referenced by the `esp32_ble_tracker` logs, focusing on the `advType: 0x0c` unhandled path. Review how advertisement data and events are processed, then determine the expected handling for the FSRKB_BT-002 data and how completion should be verified.

Written by the indexing model from the issue text.