feat(kgo): add node selector to deployment

[vitoorgomes]

What this PR does / why we need it:

The idea is to add an option to specify the node on which the KGO controller should be scheduled. This feature can be helpful when clusters have dedicated nodes for specific use cases

Special notes for your reviewer:

I'm not sure if I forgot to run something locally, in any case, just let me know

Checklist

[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

• PR is based off the current tip of the main branch.
• Changes are documented under the "Unreleased" header in CHANGELOG.md
• New or modified sections of values.yaml are documented in the README.md
• Commits follow the Kong commit message guidelines

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[pmalek]

Thanks for the contribution. Apart from the minor nit please rebase on latest main tip and resolve conflicts.

[pmalek]

This won't work on our CI.

We run these values.yaml files against an actual kind cluster and this label is not set on its nodes. You can try using something generic that we should always see on nodes like kubernetes.io/os: linux.

[vitoorgomes]

thanks for the heads up, just committed the requested changes

[pmalek]

Please run make test.golden.update to include the change in chart version: https://github.com/Kong/charts/actions/runs/14073289665/job/39429900999?pr=1264

[pmalek]

@vitoorgomes Just checking in, do you still want to contribute this change?

[vitoorgomes]

@vitoorgomes Just checking in, do you still want to contribute this change?

hey @pmalek, sorry for the late response, the last couple of weeks have been rough

I will rebase and run the make cmd and push it soon