Antalya-26.6 - Fix test_s3_cluster startup failure under db disk (duplicate shard/replica macros)

[CarlosFelipeOR]

s0_0_1 and c2.s0_0_1 both used shard1/replica2. With a remote database disk the endpoint is .../root-db-disk/test-{shard}|{replica}, so those two servers shared one S3 metadata prefix and raced each other while loading the system database: one starts, the other dies with Code: 499. Failed to get object info ... HTTP response code: 404, and the whole module errors out — 30 tests at once, in ~12.6% of db disk runs.
In this job c2.s0_0_1 came up at 07:10:33.699 and s0_0_1 at 07:10:33.701.
c2.s0_0_1's macros are not referenced by any test, so renaming its replica is enough; s0_0_1 is left as is because it takes part in the ReplicatedMergeTree tests.

Changelog category (leave one):

• Build/Testing/Packaging Improvement

CI/CD Options

Exclude tests:

• Fast test
• Integration Tests
• Stateless tests
• Stateful tests
• Performance tests
• Aarch64 tests
• All with ASAN
• All with TSAN
• All with MSAN
• All with UBSAN
• All with Coverage
• All Regression
• Disable CI Cache

Regression jobs to run:

• Fast suites (mostly <1h)
• Aggregate Functions (2h)
• Alter (1.5h)
• Benchmark (30m)
• CAS (content-addressed storage; Antalya only)
• ClickHouse Keeper (1h)
• Iceberg (2h)
• LDAP (1h)
• OAuth (5m)
• Parquet (1.5h)
• RBAC (1.5h)
• SSL Server (1h)
• S3 (2h)
• S3 Export (2h)
• Swarms (30m)
• Tiered Storage (2h)

[github-actions]

Workflow [PR], commit [cd1ec63]