This commit introduces the ability to add KML map layers from a network URL. Users can now add, view, and refresh map layers hosted online.

- A "Network Map Layer" feature has been added, allowing users to input a name and a URL (HTTP/HTTPS) to load a KML file onto the map.
- These network layers are persisted across app restarts.
- A refresh button is now available in the map controls when a network layer is visible, allowing for a manual refresh of all visible network layers.
- Individual network layers can also be refreshed from the "Manage Layers" sheet. A loading indicator shows the refresh progress.
- The "Manage Layers" bottom sheet has been updated with a new "Add Network Layer" button and a dialog to input the layer's details.

Signed-off-by: James Rich <[email protected]>

… URLs

This commit adds support for the `{s}` placeholder in custom map tile server URLs, enabling load balancing across multiple subdomains (e.g., 'a', 'b', 'c').

The `MapViewModel` now cycles through a list of subdomains and replaces the `{s}` placeholder in the URL template. This distributes tile requests and can improve map loading performance. The hint text for the URL template has been updated to reflect this new capability.

Signed-off-by: James Rich <[email protected]>

…rkers

This commit refactors the map feature by removing the flavor-specific `MapsInitializer` and centralizing map-related logic within the `feature/map` module. The explicit call to `initializeMaps` from `MeshUtilApplication` has been removed.

Marker rendering has been improved to prioritize the user's node and favorite nodes. These nodes now have a higher `zIndex` to ensure they are always displayed on top of other nodes and clusters, preventing them from being obscured.

A minor bug in custom map layer loading from a network URL has been fixed by switching from `Okio.source` to `java.io.BufferedInputStream` to prevent potential stream closing issues.

**BREAKING CHANGE:** The flavor-specific `MapsInitializer.kt` files (`google` and `fdroid` variants) have been deleted. Map initialization is now expected to be handled within the map feature module itself or through a different mechanism. This simplifies the application's entry point but may require adjustments if other parts of the app relied on this explicit, flavor-based initialization.

Signed-off-by: James Rich <[email protected]>

Signed-off-by: James Rich <[email protected]>

…anist

This commit refactors the application's permission handling by replacing the `nordic-common-permissions` library with `com.google.accompanist.permissions`.

The `AppIntroductionScreen` has been updated to use Accompanist's `rememberPermissionState` and `rememberMultiplePermissionsState` for managing runtime permissions for notifications, Bluetooth, and location. This change simplifies the permission request flow, removing the previous state management logic and custom composables like `RequireBluetooth` and `RequireLocation`.

Additionally, the `maxSdkVersion` attribute has been removed from location permissions in `AndroidManifest.xml` to ensure compatibility with the new permission handling logic across all Android versions.

Signed-off-by: James Rich <[email protected]>

This commit introduces a ViewModel to manage the application introduction flow and modularizes the navigation logic.

Key changes include:
- **IntroViewModel**: Created a new ViewModel to encapsulate the navigation logic, specifically determining the next step in the flow based on granted permissions.
- **Navigation Refactoring**: Extracted the navigation graph into a standalone `introNavGraph` function. This improves readability of the `AppIntroductionScreen` and separates UI state hoisting from navigation structure.
- **Flow Adjustment**: Reordered the introduction sequence to follow a new hierarchy: Welcome -> Bluetooth -> Location -> Notifications -> Critical Alerts.
- **Testing**: Added unit tests for `IntroViewModel` to verify the navigation sequence logic.
- **Dependencies**: Updated `build.gradle.kts` to include testing libraries such as JUnit, MockK, and Robolectric, and enabled Android resource inclusion for unit tests.

Signed-off-by: James Rich <[email protected]>

This commit refactors the map layer lifecycle management and streamlines the introduction navigation flow.

Key changes include:
- **Map Layer Management**: Decoupled Google Maps `Layer` objects (KML/GeoJSON) from the `MapViewModel` to prevent leaking view-related dependencies. Layer state is now managed within the composition using a new `MapLayerOverlay` component, which utilizes `MapEffect` and `DisposableEffect` for proper resource cleanup.
- **MBTiles Support**: Enhanced `MBTilesProvider` by implementing `AutoCloseable` to ensure the underlying SQLite database is properly closed. The `MapViewModel` now caches the current tile provider to avoid redundant allocations.
- **Improved Layer Detection**: Network map layers now automatically detect GeoJSON format based on file extensions (.geojson, .json), defaulting to KML otherwise.
- **Intro Flow Refactoring**: Centralized navigation logic in `IntroViewModel` by exposing `getNextKey` and updating `IntroNavGraph` to use this logic consistently across screens.
- **Testing**: Added comprehensive unit tests for `MapViewModel` and `MBTilesProvider` using Robolectric and MockK.
- **UI/Resources**: Updated string resources for better clarity regarding "Network" and "Map" layers, and added error messages for MBTiles file operations.

```kotlin
// Example of the new Composable-based layer management
@composable
private fun MapLayerOverlay(layerItem: MapLayerItem, mapViewModel: MapViewModel) {
    MapEffect(layerItem.id, layerItem.isRefreshing) { map ->
        // Layer initialization and attachment to the map
    }
    DisposableEffect(layerItem.id) {
        onDispose { /* Cleanup layer from map */ }
    }
}
```

Signed-off-by: James Rich <[email protected]>