client/server - handle and send 507 (insufficient storage)

[kris-watts-gravwell]

Enhancement

What is the enhancement to be made?

Cloudarchive has storage that can come and go, we need the server to send back a 507 when it doesn't have enough storage and the server to gracefully handle the 507 and engage a timer to come back again quickly

Why should we make this change? (Business justification? What problem is the feature trying to solve?)

So that if indexers are overwhelming cloudarchive endpoints we can back off gracefully

Any other comments?

Could need to be integrated into all the handlers