[GPS] Add stop address editing

[GCyganek]

Explanation of Change

WATING FOR BACKEND CHANGES THAT ALLOW SENDING MODIFIED END WAYPOINT

Adds an "Edit Stop" screen for GPS distance trips, allowing users to trim the recorded route to a shorter distance. A slider lets users set the desired endpoint; the map updates in real-time to preview the trimmed route. The trimmed end point and modified distance are persisted in Onyx (trimmedEndPoint, modifiedDistance) and cleared when the trip resumes. Reverse-geocoding is used to resolve the trimmed stop address when online.

Fixed Issues

$ #85802
PROPOSAL: N/A

Tests

1. Start a GPS distance request on a mobile device and record a trip with at least several waypoints.
2. Stop the trip recording.
3. Tap the "Edit Stop" (pencil) button that appears on the waypoints section.
4. Drag the slider to reduce the trip distance.
5. Verify that the map updates in real-time to show the trimmed route with the correct end marker position.
6. Tap "Save" and verify that the distance displayed in the GPS trip screen reflects the trimmed value.

---

1. On the Edit Stop screen, drag the slider all the way to the right (full distance).
2. Tap "Save".
3. Verify that no trimmedEndPoint or modifiedDistance is persisted and the original trip distance is shown.

---

1. After trimming and saving a trip, resume the GPS trip.
2. Verify that modifiedDistance and trimmedEndPoint are cleared and the full recorded distance is used again.

Offline tests

1. Enable airplane mode on the device.
2. Record and stop a GPS trip.
3. Open the Edit Stop screen and trim the route with the slider.
4. Tap "Save".
5. Verify that the trimmed end point address falls back to coordinate string format (e.g. 12.3456, 78.9012) instead of a reverse-geocoded address, and the trimmed distance is still correctly applied.

QA Steps

Same as tests.

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[melvin-bot]

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

1. Look at the code and make sure there are no malicious changes.
2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

[codecov]

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/CONST/index.ts	92.30% <ø> (ø)
src/SCREENS.ts	100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts	76.92% <ø> (ø)
...iou/request/step/withFullTransactionOrNotFound.tsx	95.65% <ø> (ø)
src/styles/index.ts	57.51% <ø> (ø)
src/ROUTES.ts	17.52% <0.00%> (-0.02%)	⬇️
...gation/AppNavigator/ModalStackNavigators/index.tsx	6.69% <0.00%> (-0.01%)	⬇️
...questStepDistanceGPS/Waypoints/DistanceCounter.tsx	0.00% <0.00%> (ø)
...st/step/IOURequestStepDistanceGPS/index.native.tsx	0.00% <0.00%> (ø)
...OURequestStepDistanceGPS/useGPSWaypointMarkers.tsx	0.00% <0.00%> (ø)
... and 6 more
... and 6 files with indirect coverage changes