KubeAPIWarningLogger","msg":"unknown field \"spec.deployment.podTemplateSpec.metadata.creationTimestamp\"

## Current Behavior

```
{"level":"info","ts":"2024-03-01T05:01:52Z","logger":"controlplane","msg":"gateway accepted","controller":"gateway","controllerGroup":"gateway.networking.k8s.io","controllerKind":"Gateway","Gateway":{"name":"chart-tests-kong-test","namespace":"a28261c3-c6f0-41c9-b752-ce6d5e0c20d3"},"namespace":"a28261c3-c6f0-41c9-b752-ce6d5e0c20d3","name":"chart-tests-kong-test","reconcileID":"2ae09dd2-3847-4ea7-add8-1321c0570a11","namespace":"a28261c3-c6f0-41c9-b752-ce6d5e0c20d3","name":"chart-tests-kong-test"}
{"level":"info","ts":"2024-03-01T05:01:52Z","logger":"KubeAPIWarningLogger","msg":"unknown field \"spec.deployment.podTemplateSpec.metadata.creationTimestamp\""}
```

## Expected Behavior

## Steps To Reproduce

ref: https://docs.konghq.com/gateway-operator/1.1.x/get-started/kic/install/

## Operator Version

## `kubectl version`

The issue names no files or tests; start by reproducing the installation-guide setup and inspecting the generated Gateway spec that produces the KubeAPIWarningLogger message. Determine why spec.deployment.podTemplateSpec.metadata.creationTimestamp is emitted, then verify the warning is gone without breaking gateway acceptance.

Written by the indexing model from the issue text.