[iHackSubhodip]

Summary

Apps on Maps SDK for iOS 11.x cannot resolve GoogleMapsUtils via Swift Package Manager. Package.swift declares ios-maps-sdk as from: "10.0.0", which SwiftPM reads as 10.0.0..<11.0.0.

This PR widens the range to "10.0.0"..<"12.0.0". Apps on Maps SDK 10.x are unaffected; apps on 11.x start resolving. No breaking change, no code change.

Changes

• Package.swift: ios-maps-sdk dependency is now "10.0.0"..<"12.0.0".
• .github/workflows/build.yml: the Swift package job runs two legs. pinned builds against the committed Package.resolved (10.0.0, the supported floor). latest deletes the lockfile and resolves to the newest Maps SDK in range, so both ends of the range are built and tested on every PR, and a new major that falls outside the range fails loudly.

Not changed

• Package.resolved stays at 10.0.0 on purpose, so the pinned leg proves the floor.
• Google-Maps-iOS-Utils.podspec stays at GoogleMaps ~> 10.0. Maps SDK 11.x is not published to CocoaPods, and CocoaPods is deprecated as of Maps SDK 11.0.0.

Verification

• Maps SDK 11.0.0, 11.1.0 and 11.2.0 release notes list no API changes relative to 10.15.
• Built and ran the GoogleMapsUtils scheme against Maps SDK 11.2.0 on Xcode 26.3, iPhone 17 Pro simulator: 73 Objective-C tests and 80 Swift tests passed, 0 failures, no new warnings.
• Confirmed the committed 10.0.0 lockfile resolves against the widened manifest with automatic resolution disabled.

Precedent

The Flutter google_maps_flutter_ios plugin has declared GoogleMaps >= 8.4, < 11.0 across three SDK majors for the same reason.

Fixes #574
Supersedes #575. Thanks to @Brennanium for identifying the fix.