Temporary credentials expire before a launch completes

Using temporary credentials to launch a GVL instance for example (ie, one that takes longer than 10 minutes), results in the following status message because the temp credentials have already expired.
We should be keeping those creds a bit longer to at least show the final status.
```
UNABLE TO CHECK STATUS
Health check failed: CloudBridgeBaseException: Unable to locate credentials from exception type:
```
Also, subsequent health checks can't be performed, which leads to the same message. We should recognize this and display a message that does not look like error but informs the user that features such as health checks and deleting a machine are not available with temporary creds.