[Chore] (ci): CI workflows unexpectedly fail or cancel instead of queuing under high concurrency

### Chore Type

CI/CD Configuration (GitHub Actions)

### Task Description

We are experiencing intermittent failures in the Build and Test workflow when multiple Pull Requests are submitted simultaneously. Due to runner resource limitations, we expect the workflows to queue until a runner becomes available.

However, instead of remaining in the queue, some of the later PRs create a workflow run that queues for a short period and then fails or gets cancelled automatically without ever starting execution.

### Motivation / Benefit

Can we verify if there is a timeout-minutes setting applied to the job queuing phase, or if the concurrency group cancellation logic is too aggressive? We need the jobs to wait patiently until resources are available.

@ZacBlanco could you please take a look?

### Related Files (Optional)

_No response_

### Implementation Plan (Optional)

_No response_

### Additional Context

_No response_