fix(kuma-cp): don't add postStart hook to builtin gateway even if waitForDataplaneReady: true

[lobkovilya]

Changes:

• always pass waitForDataplaneReady: false when generating builtin gateway pod
• bind envoy admin to ::1 and set waitForDataplaneReady: true in e2e-multizone

Note: even though postStart hook should be completely harmless for builtin gateway for some reason it doesn't work. Builtin gateway pod spends 3m in ContainerCreating phase, restarts, and then works as expected. @lukidzi do you know why this can happen?

Checklist prior to review

• Link to relevant issue as well as docs and UI issues --
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
• Tests (Unit test, E2E tests, manual test on universal and k8s) --
• Do you need to update UPGRADE.md? --
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label) --
• Do you need to explicitly set a > Changelog: entry here or add a ci/ label to run fewer/more tests?

[michaelbeaumont]

@lobkovilya should we backport this to 2.4?

[lobkovilya]

I don't think we should, you can work around this by adding a kuma.io/wait-for-dataplane-ready: false annotation to the builtin gateway