fix: don't wait indefinitely for k8s secrets

[mattjohnsonpint]

When initializing the kubernetes secretes provider, we should timeout if there are errors, rather than waiting indefinitely.

Some refactoring included.

[Copilot]

Pull Request Overview

This PR adds a timeout for the Kubernetes secret provider’s cache synchronization and refactors client initialization.

• Introduce a cacheSyncTimeout constant and wrap cache.WaitForCacheSync with a context timeout
• Move ctrl.SetLogger call into initialize and update newK8sClientForSecret to use ctrl.GetConfig with error handling
• Update CHANGELOG with the new fix entry

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
runtime/secrets/kubernetes.go	Implemented cache sync timeout and refactored client initialization
CHANGELOG.md	Added entry for cache sync timeout fix

Comments suppressed due to low confidence (2)

runtime/secrets/kubernetes.go:31

• Add a comment explaining the rationale for the 10-second cache sync timeout and how to adjust it if needed.

var cacheSyncTimeout = 10 * time.Second

runtime/secrets/kubernetes.go:91

• Add tests to simulate cache sync timeout and verify that timeout errors are handled correctly.

	waitCtx, cancel := context.WithTimeout(ctx, cacheSyncTimeout)