S3Queue: account failed files in tracked_file_ttl_sec and traked_files_limit

[kssenii]

Changelog category (leave one):

• Improvement

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

Account failed files in s3queue_tracked_file_ttl_sec and s3queue_traked_files_limit for StorageS3Queue.

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/

Modify your CI run

NOTE: If your merge the PR with modified CI you MUST KNOW what you are doing NOTE: Checked options will be applied if set before CI RunConfig/PrepareRunConfig step

Include tests (required builds will be added automatically):

• [ ] Fast test
• [x] Integration Tests
• [ ] Stateless tests
• [ ] Stateful tests
• [ ] Unit tests
• [ ] Performance tests
• [ ] All with ASAN
• [ ] All with TSAN
• [ ] All with Analyzer
• [ ] All with Azure
• [ ] Add your option here

Exclude tests:

• [ ] Fast test
• [ ] Integration Tests
• [ ] Stateless tests
• [ ] Stateful tests
• [ ] Performance tests
• [ ] All with ASAN
• [ ] All with TSAN
• [ ] All with MSAN
• [ ] All with UBSAN
• [ ] All with Coverage
• [ ] All with Aarch64
• [ ] Add your option here

Extra options:

• [ ] do not test (only style check)
• [ ] disable merge-commit (no merge from master before tests)
• [ ] disable CI cache (job reuse)

Only specified batches in multi-batch jobs:

• [ ] 1
• [ ] 2
• [ ] 3
• [ ] 4

[robot-ch-test-poll]

This is an automated comment for commit 7e1e4d6f282de6894c78f31deb5ddfdbdd4a2175 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
A Sync	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ success
CI running	A meta-check that indicates the running CI. Normally, it's in success or pending state. The failed status indicates some problems with the PR	✅ success
Docs check	Builds and tests the documentation	✅ 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. Integrational 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
Integration tests	The integration tests report. In parenthesis the package type is given, and in square brackets are the optional part/total tests	✅ success
Mergeable Check	Checks if all other necessary checks are successful	✅ success
PR Check	There's no description for the check yet, please add it to tests/ci/ci_config.py:CHECK_DESCRIPTIONS	✅ 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