ci: cleanup Cilium cli and connectivity test usage

[jpayne3506]

Reason for Change:

Issue Fixed:

Requirements:

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

Notes:

[Copilot]

Pull Request Overview

Centralize and streamline Cilium CLI installation and connectivity testing by moving repeated scripts into reusable templates.

• Introduce a new cilium-connectivity-tests.yaml template for running connectivity tests with retry-on-failure logic.
• Replace inline Cilium CLI install and connectivity test steps in the LSG CNI integration pipeline with references to cilium-cli.yaml and cilium-connectivity-tests.yaml.
• Comment out legacy script blocks to reduce duplication.

Reviewed Changes

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

File	Description
.pipelines/templates/cilium-connectivity-tests.yaml	Add reusable connectivity tests step with debug fallback
.pipelines/cni/lsg/lsg-cni-intergration-template.yaml	Swap inline CLI install and tests with template references

Comments suppressed due to low confidence (4)

.pipelines/templates/cilium-connectivity-tests.yaml:5

• The original inline step included retryCountOnTaskFailure: 6 to automatically retry flaky connectivity tests. Consider adding the same retry logic to this template to maintain resiliency.

 - script: | 

.pipelines/templates/cilium-connectivity-tests.yaml:6

• The previous inline step cleaned up the load-test namespace before running tests. Add kubectl delete ns load-test prior to invoking the connectivity test to ensure a clean test environment.

 if ! cilium connectivity test --connect-timeout 4s --request-timeout 30s --test ${{ parameters.skipTests }} --force-deploy 

.pipelines/cni/lsg/lsg-cni-intergration-template.yaml:190

• [nitpick] Consider removing the large commented-out Cilium CLI install block (lines 190–207) entirely, since it’s replaced by the cilium-cli.yaml template. This will reduce noise and improve readability.

 # - script: | 

.pipelines/templates/cilium-connectivity-tests.yaml:2

• [nitpick] Add a comment describing the skipTests parameter and its negation syntax (e.g., !test-name) so users understand that this config excludes specific tests.

 skipTests: '!pod-to-pod-encryption,!node-to-node-encryption,!check-log-errors,!no-unexpected-packet-drops,!to-fqdns' 

[camrynl]

✅ - after pipelines complete

[jpayne3506]

/azp run Azure Container Networking PR

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[QxBytes]

this is great for cleaning up that connectivity test redundancy