Update submodule to latest master in microsoft/main

[microsoft-golang-bot]

Hi! I'm a bot, and this is an automatically generated upstream sync PR. 🔃

After submitting the PR, I will attempt to enable auto-merge in the "merge commit" configuration.

For more information, visit sync documentation in microsoft/go-infra.

[microsoft-golang-review-bot]

Thanks! Auto-approving.

[karianna]

Failing CI

[dagood]

These errors are caused by upstream locking down linkname to reduce the fragility of libraries when standard library internals change: golang/go#67401, specifically golang/go@003683f:

---- Running command: [cmd.exe /c make.bat]
Building Go toolchain2 using go_bootstrap and Go toolchain1.
# cmd/preprofile
link: crypto/internal/backend: invalid reference to crypto/ecdsa.encodeSignature
# cmd/asm
link: crypto/internal/backend: invalid reference to crypto/ecdsa.encodeSignature
# cmd/cgo
link: crypto/internal/backend: invalid reference to crypto/ecdsa.encodeSignature
# cmd/link
link: crypto/internal/backend: invalid reference to crypto/ecdsa.encodeSignature
# cmd/compile
link: crypto/internal/backend: invalid reference to crypto/ecdsa.encodeSignature

There's a compatibility set of linknames that are still allowed for compat (defined by golang/go@41aab30) but they didn't include encodeSignature so we have to add it ourselves. (IMO this is perfectly reasonable: we're a fork, not a library, so we're able to make this change easily, and the upstream restriction lets the wider Go ecosystem be more resilient going forward.)

These errors show up one by one, so I also had to add parseSignature after fixing the first one and seeing that show up.

/cc @qmuntal

Tests no longer failing