xos-tosca occasionally fails to load current TOSCA or current protobufs

Observed the following by watching the log file:

insecurely connecting
GetSchema -- succeeds
Protobuf compilation succeeds, including loading rcord convenience wrapper
Tosca Generated

securely connecting
GetSchema -- fails many times due to connection issues
GetSchema -- succeeds
Protobuf compilation succeeds, including loading rcord convenience wrapper
Recipe starts to run
Recipe creates many objects successfully
Recipe fails on RCORDService, does not exist

xos-tosca was not restarted due to the numerous connection failures in the secure connection. I suspect what happened is that TOSCA and protobufs were compiled by the insecure connection, the core restarted due to new models (RCORDSubscriber) before the secure connection was opened, and xos-tosca continued to run using the protobufs from the original insecure connection.

The bug is that the connection failures during the secure connection did not trigger a tosca engine restart. This is because connection failures only trigger restarts if it is believed the connection had at one point been successful. Since the secure connection had never succeeded, it did not trigger restart.

Recommended fix is to restart xos-tosca if the secure connection fails after the insecure connection was successful.