[cherry-pick] chore: update Go to 1.26.0

[Manasi Gund (mancbg)]

Cherry-picking #418

Update go.mod and pipeline YAML to Go 1.26.0.

[Copilot]

Pull request overview

Cherry-picks a Go toolchain/version bump for the MOC Go module and its Azure Pipelines configuration to align local builds and CI with Go 1.26.

Changes:

• Update go.mod Go version directive to 1.26.
• Update Azure Pipelines GoTool@0 steps to use Go 1.26 for Build and Lint jobs.
• Modify make tidy to run go mod tidy -e while ignoring failures.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.

File	Description
go.mod	Bumps the module’s Go version directive to 1.26.
Makefile	Changes tidy behavior (now proceeds despite/ignores errors), impacting lint/CI reliability.
.pipelines/build.yaml	Updates CI GoTool version for Build and Lint jobs.

[Copilot]

The tidy target now ignores go mod tidy failures (leading -) and also runs with -e (proceed despite errors). This can mask real module/dependency problems and let CI/lint pass with an invalid or out-of-date go.mod/go.sum. Prefer failing the build on tidy errors (remove the leading -, and only keep -e if there is a well-justified, documented reason).

Suggested change

	-go mod tidy -e
	go mod tidy

[Copilot]

GoTool@0 was previously pinned to a patch version (e.g., 1.25.3), but is now set to 1.26. If the task resolves this to “latest 1.26.x”, builds become less reproducible; if it requires a patch version, the pipeline may fail. Consider pinning to the intended patch release (e.g., 1.26.0) to match the PR description and keep CI deterministic.

[Copilot]

Same as the Build job: the Lint job sets GoTool@0 to 1.26 instead of a pinned patch version. Consider using the exact patch (e.g., 1.26.0) for determinism and to avoid potential task/version parsing issues.