Formatting of hex encoded data views is inconsistent between interfaces

[peitschie]

Describe the bug

A byte array is encoded to a hex strings in two different ways, depending on the direction of flow.

Generally

• JavaScript => native includes a space between each hex pair (e.g., AE B1 11)
• native => JavaScript has no spaces between hex pairs (e.g., AEB111)

This inconsistency was introduced in performance optimisations added as part of https://github.com/capacitor-community/bluetooth-le/pull/701 and was noticed in https://github.com/capacitor-community/bluetooth-le/issues/717#issuecomment-2477119844

There is no defective behaviour here. However, the inconsistency is likely to be confusing for developers and people debugging.

To Reproduce The inconsistency can be seen in the JavaScript side by comparing the hex string conversion functions

Native => JS

• toHexString - contains no spaces - android and iOS
• hexStringToDataView - expects no spaces - JS

JS => native

• dataViewToHexString - contains spaces - JS
• stringToBytes - expects spaces - android and iOS

Expected behavior A consistent hex-encoding format should be used throughout.

Plugin version:

• @capacitor-community/bluetooth-le: 6.0.2