feat: Add native Ingress and Gateway API (HTTPRoute) support to Tenant CRD

[optical4eye]

Summary

Currently, the traditional RustFS Helm chart supports provisioning Ingress and HTTPRoute out of the box. However, when deploying a Tenant directly via the rustfs-operator (using bare CRDs), the Tenant resource lacks any built-in networking specs.

Describe the solution you'd like

It would be highly convenient if the Operator could natively provision networking resources, similar to how like seaweedfs-operator handle it.

Tenant spec:

spec:
  # Classical Ingress support for both API and WebUI
  ingress:
    api:
      enabled: true
      ingressClassName: nginx
      host: s3.company.local
    console:
      enabled: true
      ingressClassName: nginx
      host: s3-console.company.local 
  
  # Or modern Gateway API support
  gateway:
    api:
      enabled: true
      parentRef: company-gateway
      host: s3.company.local
    console:
      enabled: true
      parentRef: company-gateway
      host: s3-console.company.local 

Describe alternatives you've considered

Manually writing custom Ingress or HTTPRoute resources alongside every Tenant deployment, which splits a unified S3 deployment infrastructure into multiple unlinked manifests.

Additional context

This feature will completely align the Operator's declarative user experience with the traditional Helm chart, ensuring smooth, single-manifest enterprise S3 deployments.