[BUG] ScalableCluster Deployment Fails when Physical Network Adapters are already in a Team for VSwitch

**Describe the bug**
Deployment fails with network validation issues. Deployment appears to be using method to pull physical network adapters that are in an Up state only.

**To Reproduce**
Steps to reproduce the behavior:
1. Have two Physical Network Adapters in a Team
2. Created External VSwitch in Hyper-V based on the Team
3. Attempt to create deployment specifying
- VSwitch.Name = "Name of the Virtual Switch e.g VM Switch"
- VSwitch.Adaptername = "Name of the Virtual Switch Adapter e.g Hyper-V Virtual Ethernet Adapter"
- Machines.NetworkConnection.AdapterName = "Name of the Virtual Switch Adapter"

**Expected behavior**
Use an existing external VM Switch which is based of a Team shouldn't throw an error and validate it based on ALL adapters available, not just physical ones

**Screenshots**
If applicable, add screenshots to help explain your problem.


**Environment (please complete the following information):**
- AKS Edge Essentials Version 1.9.262.0
- Kubernetes version K3s
- Windows Host OS (please complete the following information):
- Edition: Windows Server Standard 2019
- Version: 10.0.17763.6659
- Virtual Machine: Hyper-V

**Additional context**
Add any other context about the problem here.

Start by reproducing ScalableCluster deployment with a Hyper-V external vSwitch backed by a teamed pair of physical adapters, using the VSwitch and Machines.NetworkConnection settings described above. Trace the deployment's network validation entry point and compare which adapters are considered; done means this configuration validates successfully without requiring only physical adapters in an Up state.

Written by the indexing model from the issue text.