This PR adds steps to migrate from ingress v2 to ingress v3.

The relevant work for ingress upgrade is:

• Feat: ingress controller align upstream module-ingress#136
• feat(ingress): changes to support ingress v3.0.1 distribution#287

The upgrade does not need a pre-apply phase, because new resources are added to the cluster during the apply, while the old ones are still present (to avoid downtime). Also, the patches have already been aligned to be applied on the new resources.

Here we are just removing the old unnecessary resources.

Upgrade paths included are:

• From 1.28.4 to 1.28.5
• From 1.29.4 to 1.29.5

Tested the second upgrade case with an On-prem cluster and the following test cases:

• Upgrade KFD 1.29.4 -> 1.29.5:
  • Ingress updated
  • All old objects are properly deleted
  • Ingress is working with:
    • SSO
    • Without SSO
    • Dual
    • Single
    • Validating Webhook Ingress is working properly: allows creation and blocks creation of duplicated ingresses on different namespaces.
    • switch dual->none->single
    • switch single->none->dual
    • integration with monitoring:
      • NGINX dashboard
      • Alerts
• Install on 1.29.5 clean (without upgrading):
  • Ingress is working
    • SSO
    • Without SSO
    • Dual
    • Validating Webhook Ingress is working properly: allows creation and blocks creation of duplicated ingresses on different namespaces.
    • integration with monitoring:
      • NGINX dashboard
      • Alerts