NO_SUCH_BUCKET and RESOURCE_UNAVAILABLE are not expected error types

[willdealtry]

trafficstars

We should not treat resource unavailable or no such bucket as expected S3 errors, as we might incorrectly decide that an object doesn't exist and can be newly created when in fact we've just not managed to talk to the storage to ascertain whether it's there or not.