Use go-canary to test Microsoft Go against community and internal repos

[qmuntal]

go-canary is a simple tool for pulling down an arbitrary Go module and testing it. We should use it to test the changes we apply to upstream Go before releasing releasing a new version.

[dagood]

There might be some overlap to clean up with:

• https://github.com/microsoft/go-lab/issues/137

[gdams]

Kicked off a test pipeline with @mertakman today: https://dev.azure.com/dnceng/internal/_build/results?buildId=2718438&view=results

[gdams]

@dagood as promised we've run a pipeline to confirm that it now works with upstream build ID set. We should be good to enable this in the pipeline again.

[dagood]

The ordering of triggering Canary is slightly wrong, submitted:

• Run canary after internal build finishes go-infra#264

Even then, a test build didn't work: https://dev.azure.com/dnceng/internal/_build/results?buildId=2719483&view=logs&j=19992227-62fb-5b50-4e29-3b72bd33eea1&t=3d27e4ef-59c0-5b63-2f42-89a3d12e6d9c&l=91

2025/05/29 20:02:51 Sending body to "[https://dev.azure.com/dnceng/internal/_apis/build/builds?definitionId=1422&api-version=7.1-preview.7"](https://dev.azure.com/dnceng/internal/_apis/build/builds?definitionId=1422&api-version=7.1-preview.7%22):
{
  "definition": {
    "id": "1422"
  },
  "parameters": "{\"DebugGoReleaseQueuePipelineOriginURL\":\"[https://dev.azure.com/dnceng/internal/_build/results?buildId=2719483\"}",](https://dev.azure.com/dnceng/internal/_build/results?buildId=2719483\%22}%22,)
  "sourceBranch": "",
  "sourceVersion": "",
  "templateParameters": {
    "upstreamRunID": "2703232",
    "version": "1.23.9-1"
  }
}

build pipeline request got 400 response; unexpected parameters: []string(nil)

When I copy paste the templateParamters into the Run dialogue of go-canary, I get this error in the UI:

Stage GoCanary job Canary_windows_1.23.9-1_ has an invalid name. Valid names may only contain alphanumeric characters and '_' and may not start with a number.
Stage GoCanary job Canary_windows_1.23.9-1_systemcrypto has an invalid name. Valid names may only contain alphanumeric characters and '_' and may not start with a number.
Stage GoCanary job Canary_linux_1.23.9-1_ has an invalid name. Valid names may only contain alphanumeric characters and '_' and may not start with a number.
Stage GoCanary job Canary_linux_1.23.9-1_systemcrypto has an invalid name. Valid names may only contain alphanumeric characters and '_' and may not start with a number.

IMO the go-canary pipeline should be updated to take the parameter as-is and escape it when necessary internally.