nightly

docs(metastore): the startup probe checks both preconditions

The configuration and operating notes still described the check as "write a throwaway object twice
with `If-None-Match` and require the second write to be rejected". The probe also reads the
object's version, overwrites it with different content, and requires a write carrying the version
it read to be rejected, so an endpoint that enforces only the first precondition (localstack up to
4.0.2) now refuses to start -- and the notes would have told an operator that such an endpoint was
fine.

Review: walgit qw-conditional-write-probe-covers-if-match, oid d32ebb6c (needs-changes, B1).