Evicted builds can be retried

[smarterclayton]

If a build fails with:

status:
  message: 'Pod The node was low on resource: [DiskPressure]. '
  phase: Failed
  reason: Evicted
  startTime: 2019-02-19T02:02:50Z

the build can be restarted by the next caller. It does not currently.

[smarterclayton]

We can also report that the pod was evicted by looking at the pod reason

2019/02/19 05:36:53 Build hypershift failed, printing logs:
2019/02/19 05:36:53 error: Unable to retrieve logs from failed build: build hypershift is in an error state. No logs are available.
2019/02/19 05:36:54 Build hyperkube failed, printing logs:
2019/02/19 05:36:54 error: Unable to retrieve logs from failed build: build hyperkube is in an error state. No logs are available.
2019/02/19 05:36:54 Build cli failed, printing logs:
2019/02/19 05:36:54 error: Unable to retrieve logs from failed build: build cli is in an error state. No logs are available.
2019/02/19 05:36:56 Build node failed, printing logs:
2019/02/19 05:36:56 error: Unable to retrieve logs from failed build: build node is in an error state. No logs are available.
2019/02/19 05:36:56 Build template-service-broker failed, printing logs:
2019/02/19 05:36:56 error: Unable to retrieve logs from failed build: build template-service-broker is in an error state. No logs are available.