rewrite 01171 test

[CheSema]

01171_mv_select_insert_isolation_long.sh is flaky. Im trying to make it stable.
The main issue that it just works slowly on some heavy builds, like tsan/debug + S3 storage.
Closes: https://github.com/ClickHouse/clickhouse-private/issues/13090

Originally tests did 100 iterations in each thread. It takes a different time depends on build type.
Now it do some amount iterations for fixed time and check that at least MIN_ITERATIONS count iterations are done.

Changelog category (leave one):

• Not for changelog (changelog entry is not required)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

...

Documentation entry for user-facing changes

• Documentation is written (mandatory for new features)

Information about CI checks: https://clickhouse.com/docs/en/development/continuous-integration/

CI Settings (Only check the boxes if you know what you are doing):

• Allow: All Required Checks
• Allow: Stateless tests
• Allow: Stateful tests
• Allow: Integration Tests
• Allow: Performance tests
• Allow: All Builds
• Allow: batch 1, 2 for multi-batch jobs
• Allow: batch 3, 4, 5, 6 for multi-batch jobs

---

• Exclude: Style check
• Exclude: Fast test
• Exclude: All with ASAN
• Exclude: All with TSAN, MSAN, UBSAN, Coverage
• Exclude: All with aarch64, release, debug

---

• Do not test
• Woolen Wolfdog
• Upload binaries for special builds
• Disable merge-commit
• Disable CI cache

[robot-ch-test-poll4]

This is an automated comment for commit f3a9e2b with description of existing statuses. It's updated for the latest CI running

✅ Click here to open a full report in a separate page

Successful checks

Check name	Description	Status
Builds	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success
Docs check	Builds and tests the documentation	✅ success
Fast test	Normally this is the first check that is ran for a PR. It builds ClickHouse and runs most of stateless functional tests, omitting some. If it fails, further checks are not started until it is fixed. Look at the report to see which tests fail, then reproduce the failure locally as described here	✅ success
Flaky tests	Checks if new added or modified tests are flaky by running them repeatedly, in parallel, with more randomization. Functional tests are run 100 times with address sanitizer, and additional randomization of thread scheduling. Integration tests are run up to 10 times. If at least once a new test has failed, or was too long, this check will be red. We don't allow flaky tests, read the doc	✅ success
Stateless tests	Runs stateless functional tests for ClickHouse binaries built in various configurations -- release, debug, with sanitizers, etc	✅ success
Stress test	Runs stateless functional tests concurrently from several clients to detect concurrency-related errors	✅ success
Style check	Runs a set of checks to keep the code style clean. If some of tests failed, see the related log from the report	✅ success
Unit tests	Runs the unit tests for different release types	✅ success
Upgrade check	Runs stress tests on server version from last release and then tries to upgrade it to the version from the PR. It checks if the new server can successfully startup without any errors, crashes or sanitizer asserts	✅ success

[CheSema]

Stateless tests flaky check (asan) --
It failed very good. I did comprehensive diagnostic.

2024-07-24 18:41:43 Reason: having stderror:  
2024-07-24 18:41:43 45/50 : not enough iterations of select_insert_action has been made from 1721838864 until 1721839294
2024-07-24 18:41:43 46/50 : not enough iterations of select_insert_action has been made from 1721838864 until 1721839294

Asan is a heavy build. The test worked 450 seconds and did 39 - 49 iterations. Which is less that threshold 50. I need just correct that threshold.

[CheSema]

Stateless Tests (msan) [2/4] ---
02481_async_insert_race_long consumed all the memory https://github.com/ClickHouse/clickhouse-private/issues/13101

[alexey-milovidov]

Ok. Btw, there is also the $SECONDS variable - the time since the script startup.

[Algunenano]

This has made the test 40x slower in release build (used to take 10 seconds, now it takes 400): https://play.clickhouse.com/play?user=play#U2VsZWN0ICogZnJvbSBjaGVja3Mgd2hlcmUgdGVzdF9uYW1lID0gJzAxMTcxX212X3NlbGVjdF9pbnNlcnRfaXNvbGF0aW9uX2xvbmcnIEFORCBjaGVja19uYW1lID0gJ1N0YXRlbGVzcyB0ZXN0cyAocmVsZWFzZSknIGFuZCBwdWxsX3JlcXVlc3RfbnVtYmVyID0gMCBvcmRlciBieSBjaGVja19zdGFydF90aW1lIGRlc2M=

And it's executed in sequential mode. So it's adding 6 minutes to all runs.

[CheSema]

Lets remove no-parallel tag. It should be fine.
I will do this.

[CheSema]

#67470