CouchDB dies if log directory is full

CouchDB dies and systemd tries to restart it over and over, if the log directory for file based logging is full.

## Steps to Reproduce
Fill the disk (for example with fallocate) where the CouchDB log is written to and watch CouchDB go down.

## Expected Behaviour
I expect, that CouchDB just stops logging and still works. The CouchDB data directory is on a separate disk and still has plenty of space to work with.

## Your Environment
Debian 12 with the official CouchDB 3.3.3 package.

Start by reproducing the failure with the filesystem containing the CouchDB file-based log full, as described in the issue. Trace the file-based logging entry point and determine how disk-full errors affect the service; done means CouchDB remains running and the separate data directory continues to work while logging stops.

Written by the indexing model from the issue text.