Use hashing for targets list comparison and enable scheduler tests

[YuliiaKovalova]

Context

AssignGlobalRequestId is a critical method in Scheduler. This change attempts to optimize the scenario in it.

Changes Made

Switch from 2 string list comparison to hashset against the second list of strings.

Testing

Covered by existing tests.

[Copilot]

Pull Request Overview

This PR refactors the way AssignGlobalRequestId matches target lists by using hash-based comparison and re-enables previously skipped scheduler tests.

• Replaced sorting-based list comparison in AssignGlobalRequestId with ComputeTargetsHash and TargetsMatch helpers
• Adjusted early exit and new-ID assignment logic
• Enabled all scheduler unit tests by removing [Fact(Skip=…)] attributes

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
src/Build/BackEnd/Components/Scheduler/Scheduler.cs	Swapped list sorting for hash checks, added hashing/matching methods, and updated assignment logic
src/Build.UnitTests/BackEnd/Scheduler_Tests.cs	Removed Skip on [Fact] attributes to enable scheduler tests

Comments suppressed due to low confidence (2)

src/Build/BackEnd/Components/Scheduler/Scheduler.cs:2249

• The combined condition incorrectly reassigns a new GlobalRequestId even when one is already set. Consider first returning immediately if GlobalRequestId is already valid, then handling the case where there are no existing requests separately.

if (request.GlobalRequestId != BuildRequest.InvalidGlobalRequestId || _schedulingData.GetRequestsAssignedToConfigurationCount(request.ConfigurationId) == 0)

src/Build.UnitTests/BackEnd/Scheduler_Tests.cs:104

• The new ComputeTargetsHash and TargetsMatch methods introduce order‐ and case‐agnostic comparisons that aren’t explicitly tested. Add unit tests covering varied target orders and casing to ensure correctness.

[Fact]

[surayya-MS]

Looks great!