Spawn host with a strange history

A spawn host was terminated by the user (and we terminated it in AWS) but subsequently "revived" and Evergreen thinks it's running. We try to extend its expiration and fail.

We should investigate if there's a sequence of buttons that a user can press in the UI to do this.