gh: workflows: clarify reference to issue #23283

Clarify that while the issue was closed as resolved, this actually only
applies to scenarios where the kind.sh script is used.

Signed-off-by: Julian Wiedmann <jwi@isovalent.com>

.github/workflows/conformance-clustermesh.yaml

@@ -336,7 +336,8 @@ jobs:
 
       # Make sure that coredns uses IPv4-only upstream DNS servers also in case of clusters
       # with IP family dual, since IPv6 ones are not reachable and cause spurious failures.
-      # Additionally, this is also required to workaround #23283.
+      # Additionally, this is also required to workaround
+      # https://github.com/cilium/cilium/issues/23283#issuecomment-1597282247.
       - name: Configure the coredns nameservers
         run: |
           COREDNS_PATCH="

.github/workflows/conformance-multi-pool.yaml

@@ -120,7 +120,8 @@ jobs:
           #  - Multi-pool IPAM only supports endpoint routes, thus we disable
           #    the local-node-route.
           #  - helm/kind-action does not support BPF host routing, so we fall
-          #    back on legacy host routing (#23283)
+          #    back on legacy host routing
+          #    (https://github.com/cilium/cilium/issues/23283#issuecomment-1597282247)
           #  - iptables-based masquerading does not support multiple non-masquerade
           #    CIDRs. Thus, we enable BPF masquerading where we can add multiple
           #    non-masquerade CIDRs.

.github/workflows/tests-clustermesh-upgrade.yaml

@@ -231,7 +231,8 @@ jobs:
 
       # Make sure that coredns uses IPv4-only upstream DNS servers also in case of clusters
       # with IP family dual, since IPv6 ones are not reachable and cause spurious failures.
-      # Additionally, this is also required to workaround #23283.
+      # Additionally, this is also required to workaround
+      # https://github.com/cilium/cilium/issues/23283#issuecomment-1597282247.
       - name: Configure the coredns nameservers
         run: |
           COREDNS_PATCH="