MT#9429 Use bond0 instead of b0 as device name for bonding

When we use b0 as device name for the bonding device, then
we get a bond0 *and* b0 device, while bond0 isn't used then.
This is slightly confusing and there's no need to do that,
since using "bond0" as device name leads to one configured
bond0 device, which operates as needed.

This also follows best practice as documented at
https://wiki.debian.org/Bonding and
https://www.kernel.org/doc/Documentation/networking/bonding.txt

Change-Id: Icfef7d34991200025821a67569b0708d24a43eef

deployment.sh

@@ -1267,7 +1267,7 @@ if "$RETRIEVE_MGMT_CONFIG" && "$RESTART_NETWORK" ; then
     # through a specific VLAN only
     ip link set dev "$INTERNAL_DEV" down # avoid conflicts with VLAN device(s)
 
-    # vlan-raw-device b0 doesn't exist in the live environment, if we don't
+    # vlan-raw-device bond0 doesn't exist in the live environment, if we don't
     # adjust it accordingly for our environment the vlan device(s) can't be
     # brought up
     # note: we do NOT modify the /e/n/i file from $TARGET here by intention
@@ -1898,8 +1898,8 @@ EOF
 auto lo
 iface lo inet loopback
 
-auto b0
-iface b0 inet static
+auto bond0
+iface bond0 inet static
         bond-slaves $EXTERNAL_DEV $INTERNAL_DEV
         bond_mode 802.3ad
         bond_miimon 100
@@ -1910,8 +1910,8 @@ iface b0 inet static
         dns-nameservers $(awk '/^nameserver/ {print $2}' /etc/resolv.conf | xargs echo -n)
 
 # additional possible bonding mode
-# auto b0
-# iface b0 inet manual
+# auto bond0
+# iface bond0 inet manual
 #         bond-slaves eth0 eth1
 #         bond_mode active-backup
 #         bond_miimon 100