Enable TLS tests on IPv6 clusters

Remove the IPv4-only restriction from TLS tests to support IPv6 clusters.
The tests use port-forwarding to localhost, which works for both IPv4
and IPv6 environments since localhost resolves appropriately in both cases.

Changes:
- Removed IPv4-only check in BeforeEach that skipped tests on IPv6 clusters
- Removed unused networking import

This allows the TLS configuration tests to run on:
- IPv4-only clusters
- IPv6-only clusters
- Dual-stack (IPv4+IPv6) clusters

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>

Author: 2 people

test/extended/apiserver/tls.go

@@ -17,7 +17,6 @@ import (
 
 	configv1 "github.com/openshift/api/config/v1"
 	"github.com/openshift/library-go/pkg/crypto"
-	"github.com/openshift/origin/test/extended/networking"
 	exutil "github.com/openshift/origin/test/extended/util"
 )
 
@@ -46,12 +45,6 @@ var _ = g.Describe("[sig-api-machinery][Feature:APIServer]", func() {
 		if isMicroShift || isHyperShift {
 			g.Skip("TLS configuration for the apiserver resource is not applicable to MicroShift or HyperShift clusters - skipping")
 		}
-
-		hasIPv4, _, err := networking.GetIPAddressFamily(oc)
-		o.Expect(err).NotTo(o.HaveOccurred())
-		if !hasIPv4 {
-			g.Skip("TLS configuration is only tested on IPv4 clusters, skipping")
-		}
 	})
 
 	g.It("TestTLSMinimumVersions", func() {