test/kubernetes/e2e/features/deployer: update tests

[sam-heilbron]

Description

Update the e2e tests that validate the behavior of the deployer

Context

Internal slack context: https://solo-io-corp.slack.com/archives/G01EERAK3KJ/p1727892654195589

• The setup/tearndown of tests (and checking objects exist) was refactoring into reusable methods
• The tests which were defined in Enterprise (https://github.com/solo-io/solo-projects/blob/main/test/kube2e/k8sgateway/k8sgateway_test.go#L276) have been introduced into oss

Interesting decisions

Testing steps

• CI passes

Locally, I setup a kind cluster, and then ran:

 go test -v -timeout 600s ./test/kubernetes/e2e/tests -run ^TestK8sGateway$/Deployer$

and

 go test -v -timeout 600s ./test/kubernetes/e2e/tests -run ^TestK8sGatewayMinimalDefaultGatewayParameters$/Deployer$

and both succeeded

Notes for reviewers

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

[solo-changelog-bot]

Issues linked to changelog:
https://github.com/solo-io/solo-projects/issues/6047

[sam-heilbron]

I renamed this file to remove the deployer from the name, since that's the package we're in

[github-actions]

Visit the preview URL for this PR (updated for commit 1fcfd94):

https://gloo-edge--pr10158-sh-improve-e2e-tests-hgl9iu3g.web.app

_{(expires Thu, 10 Oct 2024 18:11:49 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 77c2b86e287749579b7ff9cadb81e099042ef677}

[jenshu]

nit: i assume this is the original test that is being migrated here. The original test also did a simple curl/traffic test, do we want to add that here too, or do you think it's overkill?

i'm ok either way. we probably have enough other tests that do curls