introduce smart appium state verification to be able to exit with 0 from mcloud-device too

[vdelendik]

one of the use-case when appium is exited but we continue to restart mcloud-device...
zebrunner/appium#317 (comment)

1. if appium as a host not resolved then we must recreate (not even restart mcloud-device)
2. if appium is not accessible, earlier it was part of the healthcheck but seems not very useful we killed node and initiated restart
   

   mcloud-device/files/healthcheck

   Line 16 in b9f5921

   #if curl --retry 3 --retry-delay 10 -Is "http://appium:4723/wd/hub/status" | head -1 | grep -q '200 OK'

I'd say we should wait any timeout 30-60s (actual value TBD) and decide what to do next.

I believe we can start with integrating the appium status verification on the startup as of now.

[vdelendik]

also let's try to identify appium startup phase to increase waiter or ignore such state until we have understanding of the result...