Don't use `.svc` queues for pre-release builds

[dougbu]

as noted in #5277, we don't exclude builds targeting pre-release branches such as refs/heads/release/10.0-preview3 when redirecting to .svc queues. if these should be considered COGS, that's fine. but it seems more likely the redirect logic in dotnet-helix-service (RedirectHelper.IsServicingJob(...)) needs to exclude pre-release branches. this could be done w/ a check such as && !(branchName.Contains('-') || branchName.Contains("-staging")) in the private RedirectHelper.IsServicingBranch(...) method

could do something more complicated if customers create staging branches for pre-releases as well

relevant queries in historical.dashboard.json should be updated once this has been in place for a bit i.e. after the time periods we normally use have elapsed

Release Note Category

• Feature changes/additions
• Bug fixes
• Internal Infrastructure Improvements

Release Note Description

updated our internal logic to use development (not *.svc) queues when building for alpha, beta, preview, and rc releases