[Bug]: Image pull secrets not set on sync util pod causing Dockerhub rate limiting

[eysi09]

Bug

Current behavior

Due to #5336, users can get rate limited when pulling Garden images from our public Dockerhub repo if they haven't added an image pull secret with their Docker credentials to their cluster. Admittedly they shouldn't need that in the first place and we are applying for the "Docker Verified Publisher" program which should fix this.

Adding the secret fixes the issue for some of the util pods but not for the sync pod because the image pull secrets aren't set in its manifest.

We need to fix that for now, although again, if/when we're a verified publisher it shouldn't be needed in the first place.

Expected behavior

Creating the sync util pod shouldn't fail with a Dockerhub rate limit error if the user already has created image pull secrets and specified in the Garden config (under the K8s provider imagePullSecrets field).

Reproducible example

N/A

Workaround

N/A

Suggested solution(s)

We should set the imagePullSecrets on the sync util Deployment like we e.g. do for the buildkit Deployment here: https://github.com/garden-io/garden/blob/main/core/src/plugins/kubernetes/container/build/buildkit.ts#L218