Use netcracker/ingress-nginx fork in KubeMarine

[theboringstuff]

Description

Since community ingress-nginx is retired, we need to start using our own ingress-nginx builds in KubeMarine, so that we can later make fixes if necessary

Solution

• Released netcracker/ingress-nginx v1.16.0 (the same as the latest community v1.15.1)
  • Release contains necessary controller image, webhook-certgen image, manifests, chart, doc changes
  • https://github.com/Netcracker/ingress-nginx/releases/tag/helm-chart-v1.16.0
• Used this v1.16.0 version for all k8s versions in KubeMarine
  • Manifest was downloaded automatically
  • Images were resolved automatically
  • Migration patches were created
• Updated KubeMarine code to use ghcr.io/netcracker instead of registry.k8s.io
  • This is a breaking change, but only for community KubeMarine, internally we handle it normally
• Changed tests accordingly
• Updated documentation accordingly

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• There is no breaking changes, or migration patch is provided
• Integration CI passed
• Unit tests. If Yes list of new/changed tests with brief description
• There is no merge conflicts