loqrecovery: preserve information about recovery in debug zip

Current approach is to write recovery info into structured logs and rangelog.

Both of those locations are not guaranteed to be durable. Rangelog will disappear in 30 days and structured logs needs client to specifically preserve them not to be rolled.

Exposing past loss of quorum recovery events could be crucial to debugging issues later where data might become inconsistent.

Jira issue: CRDB-24550

Start by tracing how loss-of-quorum recovery information is currently written to structured logs and the rangelog, then find the debug-zip collection entry point. The issue provides no file or test names, so confirm the appropriate package and persistence format first. Done means recovery events remain available in a debug zip after logs or rangelog entries have expired.

Written by the indexing model from the issue text.