Bump the all group in /green_walking with 4 updates

[dependabot]

Bumps the all group in /green_walking with 4 updates: firebase_core, firebase_crashlytics, mapbox_maps_flutter and shared_preferences.

Updates firebase_core from 3.11.0 to 3.12.1

Commits

• 438c4c3 chore(release): publish packages
• e919293 fix(core, web): resolve type error in release mode (#17123)
• 56314d7 chore(release): publish packages (#17112)
• 5255761 feat: bump Firebase iOS SDK to 11.8.0 (#17093)
• cbbb374 feat: bump Firebase android SDK to 33.9.0 (#17092)
• a7176a8 feat: bump Firebase JS SDK to 11.3.1 (#17091)
• 43c174a chore(release): publish packages (#17056)
• See full diff in compare view

Updates firebase_crashlytics from 4.3.2 to 4.3.4

Commits

• 438c4c3 chore(release): publish packages
• 56314d7 chore(release): publish packages (#17112)
• 785bbe1 chore(crashlytics): update AGP for example app (#17064)
• 43c174a chore(release): publish packages (#17056)
• See full diff in compare view

Updates mapbox_maps_flutter from 2.6.0-rc.1 to 2.6.1

Release notes

Sourced from mapbox_maps_flutter's releases.

v2.6.1

Bug fixes 🐞

• Fix LUT not being applied to in-place updated images.
• Fix in-place updates for SDF images.
• Fix background layer not being updated if raster image was updated in-place or if color theme changed.
• Vector icons supported in location indicator layer.
  • Important: top-image, bearing-image, and shadow-image properties on LocationIndicatorLayer are now paint properties instead of layout properties.
• Fix mipmaps for images updated in place.
• Ensure background color is correctly set.
• Fixing missing vector images after style change

Dependency Updates

• Update Mapbox Maps SDK to 11.10.1 (iOS) & 11.10.2 (Android)
  • For platform-specific updates see: iOS & Android

v2.6.0

Features ✨ and improvements 🏁

• Introduce the experimental Interactions API, a toolset that allows you to handle interactions on both layers and basemap features for styles. This API introduces a new concept called Featureset, which allows Evolving Basemap styles, such as Standard, to export an abstract set of features, such as POI, buildings, and place labels, regardless of which layers they are rendered on. An Interaction can then be targeted to these features, modifying their state when interacted with. For example, you can add a TapInteraction to your map which targets the buildings Featureset. When a user taps on a building, the building will be highlighted and its color will change to blue.

var tapInteraction = TapInteraction(StandardBuildings(),
    (_, feature) {
  mapboxMap.setFeatureStateForFeaturesetFeature(feature, StandardBuildingState(highlight: true));
  log("Building group: ${feature.group}");
});
mapboxMap.addInteraction(tapInteraction);

Specific changes:

• Introduce the experimental MapboxMap.addInteractions method, which allows you to add interactions to the map.
• Introduce TapInteraction and LongTapInteraction, which allow you to add tap and longTap interactions to the map.
• Introduce FeaturesetDescriptor -- and convenience descriptors for StandardBuildings, StandardPOIs, and StandardPlaceLabels -- which allow you to describe the featureset you want Interactions to target.
• Introduce low-level methods for creating and manipulating interactive features: queryRenderedFeatures, querySourceFeatures, setFeatureState, getFeatureState, removeFeatureState, resetFeatureState
• For more guidance with using these new features see interactive_features_example.dart.
• Align tap propagation behavior on Android and iOS.
• Add support for Swift Package Manager.

Bug fixes 🐞

• [Android] Fix bug in .setStyleImportConfigProperties() where map values were not being set correctly.
• [Android] Fix throwing NPE when converting a map with null values to a Value.
• Align tap propagation behavior on Android and iOS.

Dependency Updates

• Update Mapbox Maps SDK to 11.10.0
  • For platform-specific updates see: iOS & Android

Changelog

Sourced from mapbox_maps_flutter's changelog.

2.6.1

• Update Maps SDK to 11.10.1 (iOS) and 11.10.2 (Android), introducing several bug fixes:
  • Fix LUT not being applied to in-place updated images.
  • Fix in-place updates for SDF images.
  • Fix background layer not being updated if raster image was updated in-place or if color theme changed.
  • Vector icons supported in location indicator layer.
    • Important: top-image, bearing-image, and shadow-image properties on LocationIndicatorLayer are now paint properties instead of layout properties.
  • Fix mipmaps for images updated in place.
  • Ensure background color is correctly set.
  • Fixing missing vector images after style change

2.6.0

[!IMPORTANT] The iOS minimum deployment target is now iOS 14.0.

• Update Maps SDK to 11.10.0
• [Android] Fix bug in .setStyleImportConfigProperties() where map values were not being set correctly.
• [Android] Fix throwing NPE when converting a map with null values to a Value.
• Align tap propagation behavior on Android and iOS.
• Introduce the experimental Interactions API, a toolset that allows you to handle interactions on both layers and basemap features for styles. This API introduces a new concept called Featureset, which allows Evolving Basemap styles, such as Standard, to export an abstract set of features, such as POI, buildings, and place labels, regardless of which layers they are rendered on. An Interaction can then be targeted to these features, modifying their state when interacted with. For example, you can add a TapInteraction to your map which targets the buildings Featureset. When a user taps on a building, the building will be highlighted and its color will change to blue.

var tapInteraction = TapInteraction(StandardBuildings(),
    (_, feature) {
  mapboxMap.setFeatureStateForFeaturesetFeature(feature, StandardBuildingState(highlight: true));
  log("Building group: ${feature.group}");
});
mapboxMap.addInteraction(tapInteraction);

Specific changes:

• Introduce the experimental MapboxMap.addInteraction method, which allows you to add interactions to the map.
• Introduce the experimental MapboxMap.removeInteraction method, which allows you to remove interactions from the map using an identifier mapboxMap.removeInteraction("tap_interaction_poi")
• Introduce the ability to add TapInteraction and LongTapInteraction targeting the map itself.
• Introduce TapInteraction and LongTapInteraction, which allow you to add tap and longTap interactions to the map.
• Introduce FeaturesetDescriptor -- and convenience descriptors for StandardBuildings, StandardPOIs, and StandardPlaceLabels -- which allow you to describe the featureset you want Interactions to target.
• Introduce low-level methods for creating and manipulating interactive features: queryRenderedFeatures, querySourceFeatures, setFeatureState, getFeatureState, removeFeatureState, resetFeatureState
• For more guidance with using these new features see interactive_features_example.dart.
• Add support for Swift Package Manager.

2.5.0

• Mark ClipLayer as stable.
• Updated our generated code to align with iOS and Android platforms. Specifically, the changes:
  • Update experimental symbolElevationReference property on SymbolLayer.
  • Introduce backgroundPitchAlignment property on BackgroundLayer.
  • Introduce experimental fillZOffset property on FillLayer.
  • Introduce experimental fillExtrusionBaseAlignment and fillExtrusionHeightAlignment properties on FillExtrusionLayer.
  • Mark get and set ZOffset methods on PolygonAnnotationManager, PolylineAnnotationManager, and PointAnnotationManager as experimental.

... (truncated)

Commits

• d418f8b Update versions for 2.6.1, include layer updates (#876)
• b152324 Update Standard Style Interactions Examples, Fix Bug (#865)
• a4b4651 Fix Android throwing NPE when converting a map value with null values (#848)
• 8d4d2fa Add removeInteraction, map targeting to Interactions API (#852)
• f0ad5e9 bump maps sdk to v11.10.0
• See full diff in compare view

Updates shared_preferences from 2.5.1 to 2.5.2

Commits

• 1ecb531 [shared_preferences]Fix : SetState returning future (#8398)
• c6fcb9b [shared_preferences_tool] Loosen vm_service constraint to allow for 15 (#8539)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions