Tests waste 180seconds waiting for boot

[Ham22]

Currently once programming is finished we reboot the device and wait 180 seconds.

Instead we could just wait for a few seconds (to avoid accidentally interrupting boot loader) and then sit in a loop waiting for the console to appear. This shouldn't take more than 40 seconds. If it does timeout exception should be raised.

[nikhil-zinjurde-imgtec]

Actually, it would be good to get the ota_update and ota_verify script in source control. Currently, boardfarm CI does some "magic" from Jenkinsfile with the help of ota_update.sh and ota_verify.sh which is not visible to everyone and therefore makes it difficult to understand if something gets broken around the update mechanism.

The scripts are not too complicated, so can be expanded in the Jenkinsfile and may be optimised to reduce the flashing time which is included in this 180s sleep.

On another note, following the evaluation of LAVA framework, we may be able to overhaul the update mechanism to make it more robust and responsive