bluez5-init: unify all bluetooth-init services

Unify all the different bluetooth init scripts.
The service can be started as oneshot instead of forking, as in all cases
the attach command is started daemonized in background.
Regarding the service requirements, just rely on udev so the HW itself
should be detected and ready.
Make it running before the bluetooth service, so the HW Bluetooth device
is fully ready when bluetooth service starts.

Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>

meta-digi-dey/recipes-connectivity/bluez/bluez5-init/bluetooth-init.service

@@ -1,10 +1,12 @@
 [Unit]
 Description=Initialization of the bluetooth chip
 ConditionPathIsDirectory=/proc/device-tree/bluetooth
+After=systemd-udev-settle.service
 Before=bluetooth.service
 
 [Service]
-Type=forking
+Type=oneshot
+RemainAfterExit=yes
 ExecStart=/etc/bluetooth-init start
 ExecStop=/etc/bluetooth-init stop
 

meta-digi-dey/recipes-connectivity/bluez/bluez5-init/ccimx9/bluetooth-init.service

@@ -1,14 +0,0 @@
-[Unit]
-Description=Initialization of the IW612 bluetooth chip
-ConditionPathIsDirectory=/proc/device-tree/bluetooth
-After=systemd-udev-settle.service
-Before=bluetooth.service
-
-[Service]
-Type=oneshot
-RemainAfterExit=yes
-ExecStart=/etc/bluetooth-init start
-ExecStop=/etc/bluetooth-init stop
-
-[Install]
-WantedBy=bluetooth.service

meta-digi-dey/recipes-connectivity/bluez/bluez5-init/stm32mpcommon/bluetooth-init.service

@@ -1,12 +0,0 @@
-[Unit]
-Description=CYW55512 Bluetooth Initialization
-After=network.target suspend.target
-ConditionPathIsDirectory=/proc/device-tree/bluetooth
-
-[Service]
-ExecStart=/etc/bluetooth-init start
-ExecStop=/etc/bluetooth-init stop
-Type=forking
-
-[Install]
-WantedBy=multi-user.target suspend.target