chore: bump dependencies

[Aryan-sharma11]

Purpose of PR?:

Fixes #

Does this PR introduce a breaking change?

If the changes in this PR are manually verified, list down the scenarios covered::

Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs

Checklist:

• Bug fix. Fixes #
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• PR Title follows the convention of <type>(<scope>): <subject>
• Commit has unit tests
• Commit has integration tests

[sumanthchintu]

Overall looks good
A few quick checks before merge:

The go directive is set to go 1.25.0 — can we normalize to go 1.25 if go mod tidy rewrites it?

Only the root Dockerfile bumps Go to 1.25 — please confirm other Dockerfiles (controller/operator) aren’t still pinned to an older Go version.

This PR bumps Kubernetes (v0.35.0) and Cilium (v1.19.0) together — can you confirm CI/e2e tests passed on Go 1.25 and that K8s 1.35 is an intended support target?