fix: ExternalTargetCANamespace name

[viktor-kurchenko]

The fix for connectivity tests ExternalTargetCANamespace name.
The name must be namespace specific in case of tests
concurrent run for proper CiliumNetworkPolicy provisioning.

• GKE workflow
• AKS BYOCNI workflow
• External workloads workflow
• EKS tunnel workflow failed (not enough resources for test-concurrency=5)
• EKS ENI workflow failed (not enough resources for test-concurrency=5)
• Multicluster workflow failed (looks like not related to test-concurrency param)

Fix: #2644

[michi-covalent]

ah nice good catch! 😍

[michi-covalent]

kind failure might be legitimate. i see a similar set of tests failing consistently 💭

❌ 1/13 tests failed (0/85 actions), 5 tests skipped, 0 scenarios skipped:
Test [dns-only]:

📋 Test Report [test-namespace-2]
❌ 1/11 tests failed (0/133 actions), 5 tests skipped, 0 scenarios skipped:
Test [client-egress-l7-tls-deny-without-headers]:

📋 Test Report [test-namespace-3]
❌ 1/12 tests failed (0/83 actions), 4 tests skipped, 0 scenarios skipped:
Test [client-egress-l7-tls-headers]:

📋 Test Report [test-namespace-4]
❌ 1/11 tests failed (0/93 actions), 4 tests skipped, 0 scenarios skipped:
Test [client-egress-l7-set-header]:

[viktor-kurchenko]

kind failure might be legitimate. i see a similar set of tests failing consistently 💭

Oh, no... I'll take a look! Thanks!

[viktor-kurchenko]

@michi-covalent it should work now.

[michi-covalent]

let me rebase to pick up the multicluster fix