Catch and Exit the client when we hit a SGX_BUSY Error

[mohammedpatla]

One of the Errors caught on the node that does not lead to an APP HASH is [SGX_ERROR Busy], I wonder if we can do so that when this is caught, we Exit or stop the client altogether? This would help services to reboot the secretd client and basically help with the auto-healing of the node.