Switch public and private gateway services to istio gateways

[alsergs]

1. in cr-synchroizer:
   for core-istio-mesh - required to monitor fallback routes until when they are applied in gateways - then proceed
2. include into istio helm package CRs for public and private gw services - with changed selector - to point istio gateways
3. services should be applied after cr-synchronizer reported readiness

[Ksiona]

Redesigned, so
sequence of deployment is managed by helm, according to weights.
postdeploy cr-synchronizer job has HttpRoute conditions check in GenericWaiter

[Ksiona]

There is an ability to remove cr-synchronizer component from the solution.
Helm4 has an ability to validate state of resources (adapted to helm kstatus) and manage deployment flow with the hooks

An example of annotations for HttpRoute:

metadata:
  annotations:
    helm.sh/readiness-success: |
      {.status.parents[*].conditions[?(@.type=="Accepted")].status} != "False" &&
      {.status.parents[*].conditions[?(@.type=="ResolvedRefs")].status} != "False"    
    helm.sh/readiness-failure: |
      {.status.parents[*].conditions[?(@.type=="Accepted")].status} == "False" ||
      {.status.parents[*].conditions[?(@.type=="ResolvedRefs")].status} == "False"

Programmed status can be added for Istio Gateway parent, but it can fail the route with the parent is managed by another provider

[Ksiona]

will be implemented in one PR with egress gateway fallback configuration

[alsergs]

helm.sh/readiness-success, helm.sh/readiness-failure seems not to be pat of helm4, proposal is still in draft status.
Remove these annotations from HTTPRoutes, please