[jokerttu]

Adds a Patrol integration test that navigates with a Routes API route token. #787 moves iOS to setDestinationsWithToken:completionHandler:, and nothing exercised the route token path at any level before this.

The test fetches a token with the example app's getRouteToken helper, calls setDestinations with routeTokenOptions, checks statusOk, checks that the last route segment ends at the destination, then simulates along the route until arrival. It lives in its own file, t11_route_token_test.dart, so it can run on its own with patrol test -t patrol_test/t11_route_token_test.dart.

The token fetch uses the same MAPS_API_KEY, so the key needs the Routes API enabled, both locally and in CI. A failed fetch fails the test rather than skipping it, so a broken token path cannot pass silently.

Stacked on #787.

Checks run

• Patrol, this test only: passes on the Android emulator (Android 17) and the iOS simulator (iPhone 17 Pro, iOS 26.5).
• With the token replaced by an invalid string, the test fails at the statusOk expectation (verified on iOS).
• dart format, dart analyze on the new file, and the license header check.

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I signed the CLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant documentation
• I added new tests to check the change I am making
• All existing and new tests are passing.