chore(go.mod): remove ginkgo v1

[michaelbeaumont]

Summary

Ends up being removed by go mod tidy.

[bartsmykla]

lgtm

[lahabana]

Should we do go mod tidy as part of make check?

[michaelbeaumont]

@lahabana this is also removed by make check on my machine (I assumed it did go mod tidy at some point)

[lahabana]

Weird that ci doesn't fail with some changes being present then...

[michaelbeaumont]

@lahabana I agree. I've definitely gotten the feeling there's significant non-determinism/incomprehensible logic in how go manages go.{sum,mod} given the amount of seemingly random changes I see in PRs here and other go projects...

[lahabana]

Once I looked at it and one of the core issue was that we're pulling go mods to retrieve proto dependencies like envoy-validate for .e.g pulling these go mods update go.mod. There's multiple workaround this but someone needs to spend the time.

[lahabana]

But yes go is weird with deps. I'm sure there's a logic I just don't get it :)