Add MSI testing in the CI/CD pipeline.

[gtrevi]

Closes #1037
Related #1279
Related #2422

Description

This PR adds full MSI testing for all the build configurations that are being released, i.e. Build-x64 - Debug and Build-x64-native-only - NativeOnlyRelease.

The tests are directly performed in the corresponding build pipeline, as follows:

• Install the MSI, with the features related to the current build configuration.
• Verify every single installed file against a known list of files (i.e., check_msi_installation_files_<build type>_<build configuration>.txt):
  • Check and report any missing file.
  • Check and report any extra (unexpected) file.
• Check if the eBPF platform is installed correctly:
  • Verify that all eBPF drivers are registered correctly on the system.
  • Verify that the eBPF netsh extension is correctly registered and responding to commands.
  • (optional) If the JIT option is enabled, check if the eBPF JIT service is running.
• Uninstall the MSI.

Testing

Local + CI/CD.

Documentation

Consequently to adding the automatic MSI testing in the CI/CD, the process in ReleaseProcess.md has been simplified.

Installation

n.a.

[rectified95]

LGTM. See comment about expected file list + fix grammar nit.

[dthaler]

To fix #1279, I think Install-eBPFComponents in install_ebpf.psm1 should be updated to install via the MSI rather than manually. The point is that the KM driver tests should be run after installing via the MSI.

To fix #2422, I think the legacy ability to copy individual files should be removed from deploy-ebpf.ps1.in so all installation uses the MSI.

[gtrevi]

This PR specifically adds testing to all the MSI actions.
Having other steps in the CI/CD or manual installations use the MSI instead of other forms, should be addressed in separate PR(s).

I updated the automatic closures, but I believe this PR has a very specific context, which should not be go outside testing exactly the MSI, and the MSI only.