fix: increase http client timeout

[ajbeattie]

• Increases the global timeout for the http client, as posting a job for over 1000 deployments can easily take more than the 5 second default timer
• There is a small tradeoff here that a hung PostOne or Get call could now occupy a worker for the full 30 seconds, but the risk and downside of that are both pretty low in practice. We can optionally move to per-request timeouts later, but that's a bit more involved.

[Copilot]

Pull request overview

This PR increases the HTTP client timeout used by the controller’s deploymentrecord API client to better support long-running requests (e.g., posting a cluster job when syncing large numbers of deployments).

Changes:

• Introduces a controller-level constant to define a 30-second timeout for the deployment record API client.
• Applies the new timeout by adding deploymentrecord.WithTimeout(...) when constructing the API client.

Show a summary per file

File	Description
internal/controller/controller.go	Adds and applies a 30s deployment record API client timeout during controller initialization.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 1/1 changed files
• Comments generated: 0