board/common: fix race between confd bootstrap and test_reset RPC

netopeer2 and rousette were starting as soon as confd had a PID, while
confd was still loading the startup config via sr_replace_config().  This
held a write lock on the running datastore.  A test calling test/reset
shortly after the NETCONF port opened would have its own sr_replace_config()
block on that lock for up to 60 s, at which point sysrepo timed out the
whole RPC with "SHM event 'rpc' processing timed out".

Fix by adding the usr/bootstrap condition to both management servers so
they don't accept connections until confd signals that bootstrap is complete.

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>

board/common/rootfs/etc/finit.d/available/netconf.conf

@@ -1,3 +1,3 @@
 service name:netopeer notify:none log:null env:/etc/default/confd      \
-	[12345] <pid/confd> netopeer2-server -F -t $CONFD_TIMEOUT -v 1 \
+	[12345] <pid/confd,usr/bootstrap> netopeer2-server -F -t $CONFD_TIMEOUT -v 1 \
 	-- NETCONF server

board/common/rootfs/etc/finit.d/available/restconf.conf

@@ -1,3 +1,3 @@
-service <!pid/confd> notify:none log:null env:/etc/default/confd \
+service <!pid/confd,usr/bootstrap> notify:none log:null env:/etc/default/confd \
 	[12345] rousette --syslog -t $CONFD_TIMEOUT              \
 	-- RESTCONF server