[Linux] Update GOSC test scope and handle known issues with workaround

[keirazhang]

1. Amazon Linux 2 and 2023 is not officially supported by vSphere. So here excluded it from GOSC supporting list. When it is officially supported, we can then enable its GOSC testing and ask for GOSC team to fix its failures.
2. For RHEL family OS like AlmaLinux, Rocky Linux, Oracle Linux and CentOS, their GOSC support status is as same as RHEL since release 9.0. To reduce redundant settings in linux/guest_customization/gosc_support_matrix.yml, these OS will follow RHEL's GOSC support matrix.
3. MIRACLE LINUX is a bit different. Its GOSC was supported since 8.0.3 release. So it has different support matrix.
4. VMware KB links will be redirected to Broadcom KB links. So this fix also replaced VMware KB links with Broadcom links. For VMware KB links in other test cases, I will create a new PR to change them.
5. For known issues with workaround, they are handled in linux/guest_customization/handle_gosc_known_issues.yml. Currently 3 known issues were handled:
6. From CentOS 10 and RHEL 10 , they don't have /etc/sysconfig/network-scripts, which will lead to GOSC failure on vSphere 8.0.x. In vSphere 8.0.3, an workaround fix was provided, which is to manually create this directory. Then GOSC scripts can create network config file under it.
7. From Ubuntu 23.10 release, it doesn't have hwclock by default, which leads to perl GOSC fail on 8.0.2 and earlier releases. The workaround is to install the package. 8.0.3 has fixed it, so it won't need to install the package since 8.0.3.
8. Oracle Linux 8.7 & 9.1 built-in cloud-init has bugs, which led to cloud-init GOSC failure. The workaround is to upgrade cloud-init.

[Tomorrow9]

LGTM, thanks!