[backport] #3791 ci: only check for code coverage at merge, not release

[jpayne3506]

Reason for Change:

See #3791

Issue Fixed:

Requirements:

• uses conventional commit messages
• includes documentation
• adds unit tests
• relevant PR labels added

Notes:

[jpayne3506]

/azp run Azure Container Networking PR

[Copilot]

Pull Request Overview

This PR refines the unit test pipeline to aggregate coverage results across modules and only run the code coverage check for PRs coming through the merge queue.

• Combine multiple coverage-*.out files into a single report before publishing.
• Add a conditional to run the code_coverage stage only when the branch name matches the merge-queue pattern.
• Initialize a Go workspace (make workspace) so coverage tooling includes all modules.

Comments suppressed due to low confidence (3)

.pipelines/templates/run-unit-tests.yaml:67

• The conditional hook is misaligned under stages. The - ${{ if … }}: line should be indented according to Azure Pipelines template syntax so that the code_coverage stage is correctly gated and parsed.

  - ${{ if contains(variables['Build.SourceBranch'], 'master/pr') }}:

.pipelines/templates/run-unit-tests.yaml:67

• [nitpick] Using a hard-coded branch pattern 'master/pr' can be brittle. Consider parameterizing this pattern in your pipeline variables or templates for easier updates and reuse.

  - ${{ if contains(variables['Build.SourceBranch'], 'master/pr') }}:

.pipelines/templates/run-unit-tests.yaml:30

• If no files match coverage-*.out, the tail command will fail and break the pipeline. Consider checking for file existence or using a glob-safe approach to avoid errors when coverage files are absent.

              (echo "mode: atomic"; tail -q -n +2 coverage-*.out) > coverage.cover

[azure-pipelines]

Azure Pipelines failed to run 1 pipeline(s).

[jpayne3506]

/azp run Azure Container Networking PR

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[jpayne3506]

/azp run Azure Container Networking PR

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).