Setting up measlinkbot to all GitHub workflows

[MounikaBattu17]

• This contribution adheres to CONTRIBUTING.md. (Required)
• Automatically post PR comments with images for G code changes? (Recommended for small changes)

What does this Pull Request accomplish?

This PR replaces spawningpool runner with measlinkbot (AWS runner) in all workflows (run g tests, run vi analyzer, run PR commenter.
Implements Technical Debt 2350468: Redundant / externally-maintained test runners.

Why should this Pull Request be merged?

1. Replaced spawningpool with rdss-measlinkbot-win-10-lv64 in runs-on field for all workflows.
2. run g tests: will parallelly run on four versions of LabVIEW (2020, 2021, 2022, 2023).
3. run vi analyzer: will run on LabVIEW 2023.
4. run PR commenter: will run on LabVIEW 2023.
5. Hardcoded LabVIEW path and port number in run_diff.py, run_vi_analyzer.py.
6. Skipped three Discovery Client tests as it causes LabVIEW hang at times.

Note:

• In all workflows, LabVIEW is opened and closed properly to avoid LabVIEW CLI connection error (TCP/IP connection error).
• As measlinkbot is on demand AWS runner, it takes 10-15 minutes for runners to warm and pick up the jobs after requested, thus all workflows time will be increased by 10-15 minutes.
• we can run maximum of 9 measlinkbot runners parallelly, if needed more, the workflow will simply wait (pending/queued state) for working runners to complete and then will execute pending workflows.
• If workflow fails for any abrupt reasons other than test failures, we recommend to rerun the workflow after some time.
• Changes like updating documentation on measlinkbot, removing patch work code added for spawningpool, will be made in the upcoming PR.

What testing has been done?

The checks in the PR.

[github-actions]

0 of 0 files processed successfully.

[dixonjoel]

@MounikaBattu17 It looks like this PR is ready to go. But the 'main' branch is set up to wait for 'Run LabVIEW Tests / Run G Tests' which doesn't exist in this branch with these changes. So I'm going to go ahead and disable that check, submit this, and then make one or more of the Run G Tests LV20XX required to check in.