Add NaverMap.onMapLoaded

[note11g]

Abstraction

add onMapLoaded Event listener on NaverMap widget as argument callback.

Test

tested with real device:

• Android: Galaxy S23 Ultra (Android 15, 1: 400Kbps limit speed, 2: 470Mbps full speed)
• iOS: iPhone 16 Pro (iOS 18.4, 1: 500Kbps limit speed, 2: 700Mbps full speed)

[Copilot]

Pull Request Overview

Adds a new onMapLoaded callback to the NaverMap widget that fires once the map’s data has fully loaded and rendered.

• Exposed onMapLoaded in the Dart widget and state, with documentation for its behavior.
• Wired up native load events on both iOS (NMFMapViewLoadDelegate) and Android (addOnLoadListener).
• Updated example app to demonstrate the new callback.

Reviewed Changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
lib/src/widget/map_widget.dart	Added onMapLoaded callback and state handling
lib/src/controller/map/handler.dart	Declared onMapLoaded() in control handler mixin
ios/Classes/view/NaverMapViewEventDelegate.swift	Registered and implemented mapViewDidFinishLoadingMap
ios/Classes/controller/NaverMapController.swift	Invoked channel method for onMapLoaded
ios/Classes/controller/NaverMapControlSender.swift	Added onMapLoaded() to sender protocol
example/lib/main.dart	Hooked up onMapLoaded in example usage
android/src/main/kotlin/.../view/NaverMapView.kt	Renamed listeners setup, added load listener
android/src/main/kotlin/.../controller/NaverMapController.kt	Implemented onMapLoaded in controller
android/src/main/kotlin/.../controller/NaverMapControlSender.kt	Added onMapLoaded() to sender interface

Comments suppressed due to low confidence (1)

lib/src/widget/map_widget.dart:44

• The new onMapLoaded callback is not covered by existing tests. Consider adding unit or integration tests to verify that this callback is triggered once the map finishes loading under various network conditions.

final void Function()? onMapLoaded;

[Copilot]

[nitpick] Consider having onMapLoaded accept the NaverMapController like onMapReady does, so consumers can interact with the map controller immediately when loading completes, ensuring consistency in the API design.