allow writable command even aof_last_write_status == C_ERR

[charsyam]

If someone set config set stop-writes-on-bgsave-error no,
then even though creating RDB fails, Redis allow Writable commands.

but currently, if aof_last_write_status is C_ERR, Redis always prohibits writable commands.

so. I think we should support redis can allow writable commands by admin.

so I think It is better that allow writable command when stop-writes-on-bgsave-error is no,
event though aof_last_write_status is C_ERR.

[yoav-steinberg]

This code has since been refactored (401fe7fb948f6071d5f804fc3c1fbac77286dd5) and it seems to me the logic remains that if AOF is enabled and there's an error we don't allow write commands (regardless of RDB settings).
I'm not sure I understand the original intention behind this fix and having stop-writes-on-bgsave-error determine how to behave on an AOF write error seems confusing to me.
Suggest closing.