cli: better guardrail against max-offset misconfiguration

[tbg]

Is your feature request related to a problem? Please describe.

In a recent issue¹, a user started a single node using --max-offset=5000ms
(combined with --disable-max-offset-check) to evaluate performance of an
insert workload. However, CRDB really isn't functional with a --max-offset of
that magnitude; max offsets must not exceed be a small fraction of the liveness
heartbeat interval.

We could've saved a good amount of time diagnosing this had it been impossible
to start a server with this value.

Describe the solution you'd like

Refuse to start with --max-offset outside an admissible range.

Describe alternatives you've considered

Additional context

See #127969.

Jira issue: CRDB-41304

Epic CRDB-43580

Footnotes

1. https://github.com/cockroachdb/cockroach/issues/127969#issuecomment-2288629720 ↩

[tbg]

The issue was filed initially from a report outside of our support process, but now it has also occurred in CRL support¹. Added O-support to reflect that.

Footnotes

1. https://cockroachlabs.slack.com/archives/C0KB9Q03D/p1727789620625339?thread_ts=1723502058.001399&cid=C0KB9Q03D ↩