test: use InProcessTestClusterBuilder in Azure stream reliability tests

[ReubenBond]

This fixes Azure stream reliability test flakiness caused by standalone silo processes binding real TCP ports during silo joins.

The Azure stream reliability fixture now uses InProcessTestClusterBuilder with test cluster membership and removes incidental Azure Storage clustering/gateway discovery configuration. It still exercises Azure Queue streaming and Azure-backed storage/pubsub behavior while avoiding process-hosted silo startup port collisions.

Microsoft Reviewers: Open in CodeFlow

[Copilot]

Pull request overview

This PR updates the Azure stream reliability test fixture to run using InProcessTestClusterBuilder/test-cluster membership instead of process-hosted silos, aiming to reduce flakiness from real TCP port binding collisions during silo joins while still exercising Azure Queue streaming and Azure-backed storage/pubsub behavior.

Changes:

• Migrates StreamReliabilityTests to BaseInProcessTestClusterFixture and updates cluster/client/silo configuration accordingly.
• Updates test logging calls to use the fixture-provided Logger and HostedCluster in-process cluster.
• Extends StreamTestUtils.LogStartTest to support InProcessTestCluster by logging active silo addresses.

Show a summary per file

File	Description
test/Orleans.Streaming.Tests/StreamingTests/StreamTestUtils.cs	Adds an InProcessTestCluster overload for LogStartTest to support the in-process test cluster.
test/Extensions/Orleans.Azure.Tests/Streaming/StreamReliabilityTests.cs	Switches the reliability tests to BaseInProcessTestClusterFixture and removes incidental Azure Storage clustering/gateway discovery setup.

Copilot's findings

Suppressed comments (1)

test/Extensions/Orleans.Azure.Tests/Streaming/StreamReliabilityTests.cs:964

• In StopSilo(), the action string includes "Kill and restart" when (restart, kill) is (true, true), but the current restart path always uses RestartSiloAsync() (a graceful stop + restart) and does not perform a hard kill. This log message is misleading when diagnosing test failures.

            var action = (restart, kill) switch
            {
                (true, true) => "Kill and restart",
                (true, false) => "Stop and restart",
                (false, true) => "Kill",

• Files reviewed: 2/2 changed files
• Comments generated: 1