fix(deps): update hilt to v2.59.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
com.google.dagger.hilt.android	2.57.2 → 2.59.2
com.google.dagger:hilt-android-compiler	2.57.2 → 2.59.2
com.google.dagger:hilt-android	2.57.2 → 2.59.2

---

Configuration

📅 Schedule: Branch creation - "before 9am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[claude]

Claude finished @renovate[bot]'s task in 28s —— View job

---

PR Review

• Gather context
• Review changed files
• Check CI status
• Provide review feedback

---

Summary

This is a straightforward Renovate dependency update bumping Hilt from 2.57.2 → 2.59.2 (a minor version bump of 2 patch releases).

Change Review

gradle/libs.versions.toml:11 — hilt = "2.59.2"

The change correctly updates the single hilt version reference, which is used by:

• hilt-android library (com.google.dagger:hilt-android)
• hilt-android-ksp compiler (com.google.dagger:hilt-android-compiler)
• hilt-android plugin (com.google.dagger.hilt.android)

All three artifacts share the same version reference, so this single-line change correctly updates all of them atomically. This is the right approach — no concerns here.

Assessment

No issues found. This is a safe, well-structured dependency update:

• Correctness: The version catalog pattern is correctly used — one hilt version ref drives all related artifacts consistently.
• Scope: Minor patch bump (2.57.2 → 2.59.2), no breaking API changes expected per Hilt's versioning policy.
• KSP alignment: The KSP version (2.3.6) is independent of Hilt and does not need updating.
• hiltNavigationCompose (1.3.0) is an AndroidX artifact versioned separately — no change needed there either.

CI Status

CI is currently in progress. Once Android CI passes, this PR is safe to merge.