Change BLE DFU naming according to Oltaco's bootloader for auto-updater to work

[lucidnx]

Hello! I am working on custom drone-updater script that uses @recrof 's nrf_dfu_py repo to auto update nodes in BLE range according to their firmware/bootloader names.
@oltaco already implemented per-device naming to latest nRF52 otafix bootloader release.

Naming standard: DEVICE_TYPE
where DEVICE is name of device firmware is running on and TYPE is firmware type.

This is naming @oltaco used for his bootloader (keeping it under 8 symbols):
Heltec T114 - T114_DFU
ProMicro NRF52840 - PROM_DFU
T1000e - T1KE_DFU
WioTrackerL1 - WTL1_DFU
RAK 4631 - 4631_DFU
Rak Wismesh Tag - RTAG_DFU
Xiao NRF52 BLE/SENSE - XIAO_DFU

So I suggest using naming:
Heltec T114 Repeater - T114_R
Heltec T114 Companion BLE - T114_CB
Heltec T114 Companion USB - T114_CU
Heltec T114 Room Server - T114_RS
ProMicro NRF52840 Repeater - PROM_R
ProMicro NRF52840 Companion BLE - PROM_CB
ProMicro NRF52840 Companion USB - PROM_CU
ProMicro NRF52840 Room Server - PROM_RS
T1000e - T1KE_.....
WioTrackerL1 - WTL1_....
RAK 4631 - 4631_...
Rak Wismesh Tag - RTAG_...
Xiao NRF52 BLE/SENSE - XIAO_...
...

I believe it's small change that will help with the auto-updater over BLE and also easy identification for everyone.

[oltaco]

I think the easiest change is probably the smallest, like setting a suffix to the OTA advertisment name, _R for repeater and _RS for room server? Shouldn't be too difficult and then you would know the firmware type of the device in OTA mode 👍

[lucidnx]

I would also like to have companion OTA as we can easily update these too.
There's naming issue tho. I would say adding something in between is just right..
"T114_D_CB" where D is Display, and "T114_ND_CB" no display variant.