Add 8 newly observed flaky tests to the auto-retry list
What does this MR do?
Adds 8 more test names to .flaky-tests.txt so splitic -flaky auto-retries them, following the same approach as !6687 (merged).
Why was this MR needed?
Crawled the last 100 failed CI jobs across recent MRs and main (same methodology as #39338 (closed)) and diffed the results against the current .flaky-tests.txt and #39337. Each of the 8 tests added here failed intermittently with a transient registry or Git-fetch connection reset (Docker Hub, mcr.microsoft.com, or Gitaly) - not a test-logic bug - so they're safe to auto-retry:
TestBuildCacheHelper/pwsh/no_cache_settings_provided,_no_job_cache_providedTestBuildMasking/bash/success_jobTestDockerCommandMissingTagTestDockerCommandWithPlatformTestDockerPrivilegedServiceAccessingBuildsFolderTestPwshGitCredHelper/7.2TestPwshGitCredHelper/7.3Test_StepsIntegration/script
One additional failing test was deliberately not added here: TestDockerCommandPullRetriesTransientRegistryFailure hangs for the full 15-minute test timeout on ~86% of network-faults job runs, reproducing across unrelated MRs and main. Retrying a 15-minute hang up to 3x would cost up to 45 minutes of CI time per job, so it needs an actual fix rather than auto-retry - filed separately as #39624 (closed).
What's the best way to test this MR?
No code changes; .flaky-tests.txt is data consumed by splitic at test time.
What are the relevant issue numbers?
Relates to #39337 Relates to #39338 (closed) Relates to #39624 (closed) Relates to #39625 (closed) Relates to #39626 (closed) Relates to #39627 (closed)