Can't auto recovery when encounter ENOSPC error from the filesystem

As explained in the wiki [Background Error Handling](https://github.com/facebook/rocksdb/wiki/Background-Error-Handling) section, `ENOSPC` error from the filesystem will be automatically recovered(This was introduced by @zhichao-cao in https://github.com/facebook/rocksdb/pull/8376).

In PR https://github.com/facebook/rocksdb/pull/8376, @ajkr raised a question in https://github.com/facebook/rocksdb/pull/8376#issuecomment-863809752 : if other errors encounter the same problem.

**Yes,** I encountered the `EDQUOT Disk Quota Exceeded` [(POSIx.1-2001)](https://man7.org/linux/man-pages/man3/errno.3.html) Error in the production environment, which will also cause same problems like https://github.com/facebook/rocksdb/pull/8376 that will not be able to automatically restore after a Background Error occurs.

I encountered this error code because my service is deployed in a container. Now that more and more services are using container technology, I think this problem will become more common.

Can we regard `EDQUOT` as a `NoSpace` Error, which seems to be the same property as `NoSpace`?