feat: Implement automated script for setting up WSL2 port-forwarding ports dynamically

[seanohair22]

PR Checklist

Author Mandatory (to be filled by PR Author/Submitter)

CODE MAINTAINABILITY

• Commit Message meets guidelines as indicated in the URL*
  • https://github.com/intel/AiCSD/blob/main/.github/CONTRIBUTING.md
• Tests for the changes have been added (required for bug fixes / features). If not, state why not
• Added labels (these are git labels such as bug or enhancement)
• For any API changes or service changes, updates to the documentation were made (Swagger APIs & GitHub Docs). If not, state why not
  • Will come in follow on PR
• Every commit is a single defect fix and does not mix feature addition or changes*

What are the steps to test this PR contribution?

How does a reviewer know it works?

• Run WSL_Port_Script.ps1 script in Admin Powershell on OEM Device
• Check status with the following:
  • netsh interface portproxy show all
  • Redirect output of Get-NetFirewallRule -Direction Inbound -Enabled True to a file then search for "Open SSH" (alternatively the rules should be at the bottom)

NOTE:
Remember to delete output of netfirewall file
Unset rules for port forwarding with the following:
- netsh interface portproxy delete v4tov4 listenport=22 listenaddress=0.0.0.0
- netsh interface portproxy delete v4tov4 listenport=2223 listenaddress=0.0.0.0
- netsh advfirewall firewall delete rule name="Open SSH port 22 for WSL2"
- netsh advfirewall firewall delete rule name="Open SSH Tunnel port 2223 for WSL2"

Are there any special instructions beyond standard workflow?

• WSL2 required (OEM Device setup)
• Testing requires Admin Powershell

Maintainer Mandatory (to be filled by PR Reviewer/Approving Maintainer)

QUALITY CHECKS

• Quality of code (At least one should be checked as applicable)*
  • Commit Message meets guidelines
  • Code copyright is correct
  • PR changes adhere to industry practices and standards as well as domain or language specific anti-patterns
  • Adopted domain specific coding standards (Go Coding Standards)
  • Code is adequately commented and documented
  • Confusing logic is explained in comments
  • Error and exception code paths implemented correctly
  • Tracing output are minimized and logic
• Test coverage shows adequate coverage with required CI functional tests pass on all supported platforms*
• Static code scan report shows zero critical issues*

Other information

[ejlee3]

2 things:

1. we should update the docs with the steps to use
2. should we add a follow on script to do the cleanup?

[ejlee3]

LGTM - tested on WSL2 (fresh install) and Ubuntu