ci: run kube-ovn e2e for underlay

[zhangzujian]

• Make sure you have followed Kube-OVN Code Style.

What type of this PR

• CI

Which issue(s) this PR fixes:

Some e2e cases, such as kubectl ko trace <pod>, should be run in both overlay and underlay.

WHAT

🤖 Generated by Copilot at 869e2d7

Add overlay and underlay network mode testing to GitHub Actions workflow. Modify .github/workflows/build-x86-image.yaml to use a matrix variable and different commands for each mode.

🤖 Generated by Copilot at 869e2d7

Kube-OVN modes
test overlay and underlay
autumn leaves falling

HOW

🤖 Generated by Copilot at 869e2d7

• Add a new matrix variable mode to test different network modes of Kube-OVN (link)
• Install Kube-OVN with the corresponding mode variable in the kind cluster (link)
• Set an environment variable E2E_NETWORK_MODE to select the appropriate end-to-end test cases based on the network mode (link)
• Rename the log file and the artifact name and path to include the mode variable for the make kubectl-ko-log command and the upload-artifact action (link, link)

[github-actions]

• 1. It is not clear what the "mode" parameter does in the matrix section. This should be documented or explained in a comment.
• 2. The naming convention for the artifacts generated by the E2E tests is not consistent with the naming convention used in other parts of the workflow. This could cause confusion and should be standardized.
• 3. The "sudo chown -R $(id -un). /.kube/" command in the "Setup Kind Cluster" step could potentially cause permission issues if the user running the workflow does not have ownership of the "/.kube/" directory. A more secure approach would be to use a Kubernetes configuration file that is mounted as a volume in the Kind cluster.
• 4. The "make kind-install-${{ matrix.mode }}-${{ matrix.ip-family }}" command in the "Install Kube-OVN" step should be reviewed to ensure that it is correctly installing the desired version of Kube-OVN and that it is not introducing any regressions or breaking changes.
• 5. The "make kube-ovn-conformance-e2e" command in the "Run E2E" step should be reviewed to ensure that it is correctly running the conformance tests and that it is not introducing any regressions or breaking changes. Additionally, it may be beneficial to add more detailed logging or error handling to this step to make it easier to diagnose failures.