Restructure Helm values.yaml to use idiomatic nested structure

[kelos-bot]

What would you like to be added?

The current values.yaml uses a flat naming convention for spawner and token-refresher resource configuration:

spawnerResourceRequests: ""
spawnerResourceLimits: ""
tokenRefresherResourceRequests: ""
tokenRefresherResourceLimits: ""

In PR #783, controller resources were added using a more idiomatic nested Helm structure:

controller:
  resources:
    requests: ""
    limits: ""

The spawner and token-refresher values should be migrated to the same nested pattern for consistency:

spawner:
  resources:
    requests: ""
    limits: ""
tokenRefresher:
  resources:
    requests: ""
    limits: ""

This would also allow future configuration for each component to be naturally grouped under its key (e.g., spawner.image, tokenRefresher.image).

Why is this needed?

• Consistency: the controller already uses the nested pattern
• Follows standard Helm conventions (e.g., similar to how upstream charts structure resources)
• Better extensibility for future per-component configuration

Per reviewer discussion in #783 (comment).

[kelos-bot]

🤖 Kelos Task Status

Task kelos-triage-789 has succeeded. ✅

[kelos-bot]

🤖 Kelos Agent @gjkim42

Kelos Triage Report

Kind: kind/cleanup
Priority: priority/important-longterm — Quality-of-life improvement for Helm chart consistency; not blocking any functionality
Actor: actor/kelos — Concrete refactor with clear before/after structure; scope is well-defined across values.yaml, deployment template, and Go flag parsing

Status: STILL VALID

Evidence:

• internal/manifests/charts/kelos/values.yaml still uses flat keys: spawnerResourceRequests, spawnerResourceLimits, tokenRefresherResourceRequests, tokenRefresherResourceLimits (lines 15-19)
• internal/manifests/charts/kelos/templates/deployment.yaml references these flat values (lines 57-71)
• No merged PRs or commits reference issue Restructure Helm values.yaml to use idiomatic nested structure #789 or related restructuring work
• The controller nested pattern mentioned in the issue (from PR Add configurable resource requests/limits for the controller #783) does not appear in values.yaml, suggesting the controller resources may be handled differently or PR Add configurable resource requests/limits for the controller #783's pattern was not yet merged into this structure — either way, the spawner/token-refresher values remain flat

Duplicates found: None found. #779 (controller resource configuration) is related context but addresses a different component.

Recommendation: KEEP OPEN — The change involves updating values.yaml, the deployment template, and potentially the Go CLI flag parsing to accept the new nested paths. Well-scoped for autonomous implementation.