Reverse geocoding returns localized punctuation (Arabic comma) in qualifiedName causing backend failures

Nobody has claimed this yet.

## Environment
- iOS: 26.x
- Xcode: 16.x
- MapboxMaps: 11.16.1 / 11.21.0
- MapboxGeocoder.swift: ~> 0.15
- MapboxSearch: 2.16.1

**Observed behavior and steps to reproduce**
## Issue

When performing reverse geocoding, the value of `placemark.qualifiedName` sometimes contains a non-standard comma character (`،`) instead of a normal comma (`,`).

Example:
"2nd Main Rd 43، 560016 Bengaluru، India"

**Steps to reproduce**

1. Perform reverse geocoding:
ReverseGeocodeOptions(coordinate: location)
2. Get result:
placemark.qualifiedName
3. Observe that returned address contains `،` instead of `,`

## Impact

- Causes backend failures when sending address
- Inconsistent behavior across regions/devices

## Expected behavior

- Address should use standard comma (`,`)
- Or provide a way to control formatting/locale

Start by reproducing reverse geocoding with ReverseGeocodeOptions and inspecting placemark.qualifiedName across the reported iOS and MapboxSearch versions and locales. Trace where the qualifiedName address is formatted; done means the result consistently uses a standard comma or provides a documented locale or formatting control for this case.

Written by the indexing model from the issue text.