fix(consistency): enable state table sanity check only in strict consitency mode

[stdrc]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

We have to disable state table sanity check when in non-strict consistency mode.

I've tried another approach (main...rc/mem-table-sanity), that is to still enable sanity check but ignore any error returned by mem table, however it turns out to be a bit strange, in that mem table have to do anything that is supposed to do if sanity check succeeds when it actually fails.

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[stdrc]

Running a longevity test with unsafe_enable_strict_consistency: false: https://buildkite.com/risingwave-test/longevity-test/builds/1406

[stdrc]

Running a longevity test with unsafe_enable_strict_consistency: false: https://buildkite.com/risingwave-test/longevity-test/builds/1406

Longevity test passed, demonstrating that user can toggle strict mode to false without significant issue.

[stdrc]

The "insane" mode that help simulate inconsistent stream still has some issue, I'm still working on it to bring it to our special version of longevity test, but that is not quite related to the enable_strict_consistency toggle. We can actually publicize the config after this PR.

[wenym1]

Rest LGTM

[wenym1]

LGTM!