[No QA] Docs updates for E/A#93848 Document commuter mileage exclusion in Distance rates

[MelvinBot]

Explanation of Change

Documents the commuter mileage exclusion feature added to workspace Distance rates in #93848 (App-side of Expensify/Expensify#642599).

The help site had no coverage of commuter exclusions. This updates the NewDot Set Distance Rates article (docs/articles/new-expensify/workspaces/Set-distance-rates.md) to explain:

• How to exclude commuter miles from distance expenses — the admin workflow under Distance rates > Settings > Exclude commutes, including the two options (Do not exclude commutes / Exclude a fixed distance per claim) and the Distance field.
• What members see when commuter miles are excluded — the Original / Removed / reimbursable breakdown, the Removed … commuter miles based on workspace distance settings system message, and the map/GPS-only requirement (Map or GPS distance required).
• Two FAQ entries covering the manual/odometer restriction and the effect on existing expenses.

⚠️ Feature is currently behind a beta

The Exclude commutes setting is gated behind the COMMUTER_EXCLUSIONS beta (CONST.BETAS.COMMUTER_EXCLUSIONS) and is not yet visible in the live UI. Live verification confirmed the Distance rates Settings page currently shows only Unit, Default category, and Track tax — no Exclude commutes row. All labels in this doc were taken verbatim from the shipped src/languages/en.ts strings. Please hold this PR until the feature is generally available, and confirm the labels once it's live.

Fixed Issues

Docs follow-up for #93848.

Tests / QA

Docs-only change. Verify the rendered Set Distance Rates article reads correctly and the new headings/links render as expected.

---

@fedirjh, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

[MelvinBot]

The only failing check is Check independent approval — there's nothing to fix in the code.

That check ("Verify peer review") isn't a test or lint failure. It fails because the PR hasn't yet received an approval from an independent reviewer (someone other than the author). It's a process gate, not a code issue, so pushing a code change won't clear it — it'll go green once an eligible reviewer approves.

Every other check is green or skipped; build is still pending (not failed).

Note this PR is intentionally on hold: the documented Exclude commutes feature is still gated behind the COMMUTER_EXCLUSIONS beta and isn't live in the UI yet, so this shouldn't merge until the feature is generally available regardless of the approval check.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://dbdab15d.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/workspaces/Set-distance-rates