feat: sending maps

[cimigree]

closes #1592
Stacked on #1693 and #1697
Adds the UI for sending map screens
Uses navigation.replace throughout to prevent someone going back to where they shouldn't
Uses the api to get the progress of the download
You can't really get there now as I haven't wired up the receiving end yet... So as soon as we have the receiver end and they can accept a map we can get to these screens.
In the meantime, choose a device and it will take you to the "Waiting" screen and then you can see these two screens.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​osm_borders/​maritime_10000m@​1.1.0
	npm/​@​formatjs/​cli@​6.8.2
	npm/​@​types/​lodash.isequal@​4.5.8
	npm/​@​react-native/​typescript-config@​0.76.9
	npm/​@​react-native/​metro-babel-transformer@​0.76.9
	npm/​@​types/​lint-staged@​13.3.0
	npm/​@​types/​react-native-zeroconf@​0.13.1
	npm/​@​comapeo/​nodejs-mobile-react-native@​18.20.4-2
	npm/​@​types/​react-native-indicators@​0.16.6
	npm/​@​react-native/​metro-config@​0.79.5
	npm/​@​tanstack/​eslint-plugin-query@​5.91.2
	npm/​@​types/​semver@​7.7.1
	npm/​@​react-navigation/​native-stack@​7.3.21
	npm/​@​react-navigation/​native@​7.1.28
	npm/​@​mapeo/​mock-data@​5.0.0
	npm/​@​react-navigation/​bottom-tabs@​7.14.0
	npm/​@​comapeo/​cloud@​0.3.0
	npm/​@​formatjs/​intl-pluralrules@​6.2.2
	npm/​@​react-navigation/​stack@​7.7.2
	npm/​@​types/​jest@​30.0.0
	npm/​@​formatjs/​intl-getcanonicallocales@​3.2.1
	npm/​@​babel/​preset-env@​7.28.5
	npm/​@​types/​mocha@​10.0.10
	npm/​@​comapeo/​core@​5.2.1 ⏵ 5.4.1			+1
	npm/​@​formatjs/​intl-locale@​5.2.1
	npm/​@​react-native-vector-icons/​octicons@​20.4.0
	npm/​@​react-native-documents/​picker@​12.0.1
	npm/​@​types/​react@​19.2.7
	npm/​@​babel/​runtime@​7.27.1 ⏵ 7.28.4				-1
	npm/​@​react-native-vector-icons/​fontisto@​12.4.0
	npm/​@​types/​utm@​1.1.4
	npm/​@​formatjs/​intl-relativetimeformat@​12.2.2
See 33 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @browserstack/ai-sdk-node is 100.0% likely obfuscated Confidence: 1.00 Location: Package overview From: package-lock.json → npm/@wdio/browserstack-service@9.21.0 → npm/@browserstack/ai-sdk-node@1.5.17 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@browserstack/ai-sdk-node@1.5.17. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @browserstack/ai-sdk-node is 98.0% likely obfuscated Confidence: 0.98 Location: Package overview From: package-lock.json → npm/@wdio/browserstack-service@9.21.0 → npm/@browserstack/ai-sdk-node@1.5.17 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@browserstack/ai-sdk-node@1.5.17. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @react-native/debugger-frontend is 96.0% likely obfuscated Confidence: 0.96 Location: Package overview From: package-lock.json → npm/@react-native/debugger-frontend@0.81.5 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@react-native/debugger-frontend@0.81.5. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report