What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Deletes e2e/utils/ and moves its contents into the domain packages (k8s/, grove/, log/, measurement/).

The domain packages (k8s/, grove/, diagnostics/) already exist but their methods still delegate to utils.* functions, creating two layers for every operation. The utils/ package has no clear domain — it's a dumping ground with node helpers, polling, Grove resource operations,
conversions, and logging all in one place. Removing it eliminates the indirection and puts every function in the package that owns its domain.

What moved where:

• utils/logger.go → new standalone e2e/log/ package
• utils/polling.go → k8s/polling.go (already existed, removed duplicate)
• utils/conversions.go → k8s/conversions.go (already existed, removed duplicate)
• utils/node.go → k8s/nodes/nodes.go (standalone functions added)
• utils/grove_config_k8s.go → grove/config/config.go (already existed, removed duplicate)
• utils/topology.go, utils/kai_topology.go → grove/topology/, grove/podgroup/ (already existed, removed duplicates)
• utils/grove_resources.go, utils/k8s_client.go, utils/cr_client.go → split across grove/workload/standalone.go, k8s/nodes/, k8s/pods/, k8s/clients/, k8s/unstructured.go
• utils/measurement/ → e2e/measurement/ (moved out of utils, no code changes)
• All imports updated across setup/, tests/, diagnostics/, grove/, testctx/
• e2e/utils/ deleted

Which issue(s) this PR fixes:

Fixes #517

Special notes for your reviewer:

This is a pure move/delete refactor — no behavioral changes. Every function either already had an equivalent in a domain package (and the utils/ duplicate was removed) or was moved as-is to the appropriate domain package. Build and unit tests pass.

Does this PR introduce a API change?

NONE

Additional documentation e.g., enhancement proposals, usage docs, etc.: