fix(settings): use replace navigation to skip settings route when viewing usage

[MattPua]

Problem

Clicking "View usage & spend analysis" in settings dumped you on the new-task chat input instead of the usage page.

The button called closeSettings() (async history.back()) then navigateToUsage(). The back-navigation won the race and landed on the previous route.

Changes

• navigateToUsage() takes an optional replace flag.
• Button now resets the settings store and navigates to /usage with replace: true, so back from /usage still skips settings, with no racing history.back().

How did you test this?

• pnpm --filter @posthog/ui typecheck + biome lint pass.

Automatic notifications

• Publish to changelog?
• Alert Sales and Marketing teams?

---

Created with PostHog Code

[trunk-io]

Merging to main in this repository is managed by Trunk.

• To merge this pull request, check the box to the left or comment /trunk merge below.

After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here

[github-actions]

React Doctor found no issues in the changed files. 🎉

_{Reviewed by React Doctor for commit 5903846.}

[greptile-apps]

_{Reviews (1): Last reviewed commit: "fix(settings): use replace navigation to..." | Re-trigger Greptile}

[github-actions]

Trivial navigation fix — adds an optional replace flag to avoid leaving the settings route in history. No business logic, data model, or API changes.