Port BluetoothLEHelper from 7.x

**Source**: Microsoft.Toolkit.Uwp.Connectivity (7.x)
**Destination**: CommunityToolkit.WinUI.Helpers (8.x) — not yet ported

## Description

The BluetoothLEHelper class provides functionality to easily enumerate, connect to and interact with Bluetooth LE Peripherals.

## Prerequisites

None identified.

## Porting Basics

- [ ] Namespace updated to `CommunityToolkit.WinUI.*`
- [ ] Code for UWP, WinUI3 and Uno Platform consolidated
- [ ] Desired MultiTargets configured
- [ ] Sample code migrated
- [ ] Concept docs migrated
- [ ] Tests migrated and passing

## Quality Evaluation

See [Porting Criteria](https://github.com/CommunityToolkit/Windows/wiki/Component-Quality-Evaluation) for detailed evaluation guidance.

- [n/a] UX: Accessibility reviewed
- [n/a] UX: Visual design reviewed
- [n/a] UX: Interaction patterns appropriate
- [ ] DX: API surface reviewed
- [ ] DX: API flexibility appropriate
- [ ] DX: Documentation updated
- [ ] MX: Breaking changes documented
- [ ] MX: Domain isolation appropriate
- [ ] MX: Test coverage adequate

## Tracking Gaps

*No gaps identified — porting work not yet started.*

## Closing

- [ ] All Porting Basics complete
- [ ] Quality Evaluation reviewed
- [ ] Gaps filed as sub-issues

---

## 7x Documentation Inventory

**Docs ported to 8x**: n/a

**Docs not in 8x**:
- Summary
- BluetoothLEHelper class
- Properties
- Methods
- Events
- ObservableBluetoothLEDevice class
- Properties
- Methods
- ObservableGattDeviceService
- Properties
- ObservableGattCharacteristics
- Properties
- Methods
- Example

## 7x Source Inventory

**Source already ported to 8x**: n/a

**Source not ported to 8x**: n/a

## Notes

- Not currently planned for porting. Open to community interest.
- **Archive redirect**: https://learn.microsoft.com/en-us/dotnet/communitytoolkit/windows/archive/bluetoothlehelper

Comienza con la documentación archivada de BluetoothLEHelper e inspecciona la distribución de componentes de CommunityToolkit.WinUI.Helpers 8.x para determinar dónde deben ubicarse el código fuente, los ejemplos, la documentación conceptual y las pruebas. Se considera completado cuando se hayan completado las listas de comprobación “Porting Basics” y “Quality Evaluation”, incluidos los destinos configurados, las pruebas migradas, la documentación, la revisión de la API y una cobertura de pruebas adecuada.

Escrito por el modelo de indexación a partir del texto del issue.