Determine root cause of Aerospike stop-writes in a new simple command

To avoid the devastating impact of Out Of Memory (OOM) errors in databases, Aerospike introduces a protective measure called the stop-writes condition, which acts as a sentinel to prevent database unrecoverable states. The `show stop-writes` command is introduced to help navigate through stop-writes scenarios and ensure data safety. Various configurations can trigger stop-writes, including restricting set sizes or namespace limits. When encountering stop-writes, using the `asadm` tool with its `manage config` command allows for temporary solutions, such as raising thresholds or freeing up space, until a more permanent fix is implemented.