Remove DNS length validation for non-DNS related resource names

[damyan]

Currently we enforce 64 character length for resource names by using a kubernetes API DNS validation mechanism. We shoould loosen up this requirement by allowing longer resource names.

An example with ConfigMap in kubernetes, which allows 254 character length for resource names.

[ushabelgur]

We are using ValidateObjectMetaAccessor from apiMachinery package to validate names. This functions validates object's metadata on creation. It expects that name generation has already been performed. (

ironcore/internal/apis/networking/validation/networkinterface.go

Line 23 in 081df69

allErrs = append(allErrs, apivalidation.ValidateObjectMetaAccessor(networkInterface, true, apivalidation.NameIsDNSLabel, field.NewPath("metadata"))...)

)

This is the validation used for ConfigMap in kubernetes https://github.com/kubernetes/kubernetes/blob/c26c59a0b85a92194a5ce0ce72f67eac2b84e1fd/pkg/apis/core/validation/validation.go#L6899C52-L6899C70
https://github.com/kubernetes/kubernetes/blob/c26c59a0b85a92194a5ce0ce72f67eac2b84e1fd/staging/src/k8s.io/apimachinery/pkg/api/validation/generic.go#L37
it follows DNSSubDomain format : a lowercase RFC 1123 subdomain consist of lower case alphanumeric characters, '-' or '.', and start and end with an alphanumeric character
where as current validation follows DNSLable format: a lowercase RFC 1123 label consist of lower case alphanumeric characters or '-', and must start and end with an alphanumeric character (No . allowed like in subdomain)

@afritzler can we use the same method used by configMap in our validation ? question is do we want to allow . also in the names then ?