fix: supportsEndpointSlice needs to be set correctly

[ronething]

It is necessary to determine whether the call here is accurate. In subsequent functions, resolveServiceEndpoints(tctx, c, serviceNN, true, nil)

the param supportsEndpointSlice We set it to true by default, which theoretically would cause problems on k8s clusters that do not support EndpointSlice

Originally posted by @ronething in #220

[BeanBois]

Hi @ronething , I will like to help in this issue. I am quite new to the repository but I have read the controllers code in internal/controllers and have seen that some of the controllers (like apisixroute_controller.go and gatewayproxy_controller.go) have their own supportEndpointSlice field, and their own logic of doing this support endpoint slice check with pkgutils. Knowing this, will it be desired to have IngressClassV1beta1Reconciler to have a SupportsEndpointSlice field within its struct, and use it within the addProviderEndpointsToTranslateContext() func? This will require the addProviderEndpointsToTranslateContext() function to have an additional argument of supportsEndpointSlice bool, which cascades down into ProcessIngressClassParameters() and ProcessGatewayProxy() functions within utils.go. This effectively cascades down to other controller calling these 2 functions, and my fix for it is to likewise have their struct to have a supportEndpointSlice field. Is this fix proposed suitable?

[Baoyuantop]

Hi @BeanBois, thanks for your contribution. I've reviewed your draft PR, and the solution is fine. Please continue with your PR.

[BeanBois]

Hi @Baoyuantop I require a contributor with write access to approve my pull request for the workflow to start. Could you do this for me?