[release/10.0] Run networking stress tests on .NET 10 releases

[rzikm]

Customer Impact

None, test-only change to enable regular stress test runs on release/10.0 branch

Regression

• Yes
• No

Testing

Stress test will be triggered for this PR

Risk

Low, test-only change.

[Copilot]

Pull Request Overview

This PR updates the branch filters for networking stress test pipelines to run on .NET major release branches instead of staging branches. The pattern is changed from release/*-staging to release/*.0 to align with the actual release branch naming convention.

Key Changes:

• Updated scheduled build branch filters in HTTP and SSL stress test pipelines
• Changed pattern from release/*-staging to release/*.0 to match major release branches (e.g., release/10.0)

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
eng/pipelines/libraries/stress/ssl.yml	Updated scheduled build branch filter to target major release branches
eng/pipelines/libraries/stress/http.yml	Updated scheduled build branch filter to target major release branches

[rzikm]

/azp run runtime-libraries stress-http

[rzikm]

/azp run runtime-libraries stress-ssl

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

[rzikm]

Stress test runs pass, other failures are unrelated

[rzikm]

/ba-g Stress test runs pass, other failures are unrelated

[karelz]

@artl93 this is test-only / test-infra change only. It is ready for servicing. Now that 10 is GA, will you be merging these? Should we tag you? Or should I run ti by Tactics?

[artl93]

infra changes are tell mode.
I'll approve and merge -- though I think we need a new flow.