Irrelevant status related warn logs spammed when using Gateway v2

[shashankram]

Gloo Edge Product

Open Source

Gloo Edge Version

main

Kubernetes Version

1.27.3

Describe the bug

When using Gateway v2, I see the following log message being spammed:

{"level":"warn","ts":"2024-04-22T18:02:49.868Z","logger":"gloo.v1.event_loop.setup.reporter","caller":"reporter/reporter.go:394","msg":"failed to write status state:Accepted  reported_by:\"gloo\" for resource infra-http-gateway: error reading before applying status: infra.infra-http-gateway does not exist","version":"1.0.0-dev"}

Per @lgadban: "this is unintended and undiagnosed issue with using the legacy envoy syncer — all the existing reporting doesn’t “work” when doing ggv2 style translation and this is likely an artifact of that"

Expected Behavior

Legacy status reporting needs to be made conditional for Gateway v2.

Steps to reproduce the bug

1. Deploy Gateway v2
2. Create Gateway and HTTPRoute
3. Check gloo controller logs

Additional Environment Detail

Kind cluster

Additional Context

No response