fix(gloo): Use correct route table name in case service name was overwritten

[mdolinin]

Steps to reproduce bug:

• Create Canary resource with service.name set and provider gloo
  For example:

  provider: gloo 
  service:
    name: podinfo-flagger

• flagger will create RouteTable with name podinfo-flagger
• But then in logs it will error that query error: routetables.gateway.solo.io for name podinfo

This PR will use same func and names for GetRoutes as for Reconcile.

PR contains:

• fix for issue
• update gloo helm chart to latest stable 1.12.31
• remove check for gateway deployment in tests. Because gateway functionality is removed from a standalone pod, and is now included in the Gloo Edge control plane pod. https://docs.solo.io/gloo-edge/latest/operations/upgrading/v1.12/

[stefanprodan]

@mdolinin can you please bump Gloo Helm chart version to latest in e2e tests here: https://github.com/fluxcd/flagger/blob/main/test/gloo/install.sh#L5

[mdolinin]

@mdolinin can you please bump Gloo Helm chart version to latest in e2e tests here: https://github.com/fluxcd/flagger/blob/main/test/gloo/install.sh#L5

@stefanprodan Updated to the latest stable 1.12.31

[mdolinin]

@stefanprodan can you please approve CI workflow to execute. I have made necessary change to test. And updated PR description. Thanks.

[mdolinin]

@stefanprodan Can we re-run [e2e-test (nginx)] (https://github.com/fluxcd/flagger/actions/runs/3322155362/jobs/5490871791#logs)? I could not understood how my last commit impacted that.

[stefanprodan]

LGTM

Thanks @mdolinin 🏅