feat: add collision behavior support for Advanced Markers

[lorenc-tomasz]

Pull request

Please ensure this PR targets the dev branch and follows the project conventions.
CI already runs linting, formatting, and build checks automatically.

---

Before submitting

• This PR targets the dev branch (not main)
• Commit messages follow the semantic-release format
• No debug logs or sensitive data included

---

Summary

Adds Map ID plumbing and collision behavior support for Advanced Markers on Android and iOS while preserving the existing SVG-based marker API.

• Adds optional initialProps.mapId configuration.
• Adds optional RNMarker.advanced configuration.
• Adds the extensible RNMarker.advancedOptions configuration object.
• Adds advancedOptions.collisionBehavior.
• Supports all three Google Maps collision behaviors.
• Uses required as the default collision behavior.
• Reports an INVALID_ARGUMENT map error when an Advanced Marker is requested without a map ID.
• Reports an INVALID_ARGUMENT map error when advancedOptions is provided without advanced: true.
• Falls back to a standard marker when the configured map does not expose the Advanced Markers capability.
• Adds the onMapCapabilitiesChange callback for runtime capability updates.
• Adds dedicated Map ID and Advanced Markers examples.

The existing iconSvg pipeline is reused. Native pin customization is not included.

---

Type of change

• Feature
• Fix
• Refactor
• Internal / CI
• Documentation

---

Scope

• Android
• iOS
• JS
• Example App
• Docs

---

Related

N/A

---

Additional notes

mapId remains optional for regular maps and standard markers.

A map ID is required when marker.advanced is true. When advanced is false or omitted, the existing standard marker implementation is used.

Collision behavior can be configured through:

{
  advanced: true,
  advancedOptions: {
    collisionBehavior: 'required-and-hides-optional',
  },
}

[lorenc-tomasz]

Hi,
@pinpong What do you think about adding that to library? :)