PR #7399 merged without successful status checks (mapbox-navigation-android)

Nobody has claimed this yet.

:wave: Hey there! It's [Changebot](https://github.com/mapbox/changebot), and I help repositories follow our [engineering](https://github.com/mapbox/engineering) best practices. My magic wand found some things I wanted to highlight for your review:

Item | Current status | Required? | Best practice guidelines
--- | --- | --- | ---
Run unsuccessful: [ci/circleci: release-workflow/release-snapshot-start](https://circleci.com/workflow-run/4e84d2f4-d2c0-4b22-b5d2-a731e19aba3c) | pending | optional | success
Run unsuccessful: [ci/circleci: default/mobile-metrics-dry-run](https://circleci.com/workflow-run/4f33d5a1-dd62-417c-a808-62be92529b38) | pending | optional | success
Run unsuccessful: [publisher-deployer](https://github.com/mapbox/mapbox-navigation-android/runs/15392936715) | neutral | optional | success
Run unsuccessful: [release-workflow](https://github.com/mapbox/mapbox-navigation-android/runs/15392935698) | null | optional | success

The following PR was merged without the status checks passing: https://github.com/mapbox/mapbox-navigation-android/pull/7399

Can you take a look at these best practices and make any adjustments if needed?

Please tag `@mapbox/security-and-compliance` on this issue if you have any questions

Review PR #7399 and the linked CircleCI and GitHub run records first. Trace the repository’s status-check and release workflow configuration to determine why the listed checks were not successful at merge; done means the affected checks complete successfully and the reported condition does not recur.

Written by the indexing model from the issue text.