fix(android): report granted location permission through the mobile bridge

Reproduction\n\n1. Generate an Android app with Craft revision 26d927f7f927e4db2c85c3df89368d3f3b745dba and enableGeolocation: true.\n2. Launch it with Android location permission already granted.\n3. In the WebView, call permissions.check('location') from craft-native/mobile or @stacksjs/mobile.\n4. Call permissions.request('location') if the result is not granted.\n\n## Actual\n\nThe API does not return granted. The UI remains on the request label and exposes its Open device settings recovery link, which the Stacks NativePermissionButton renders only for denied or restricted status.\n\n## Expected\n\nIf Android has already granted ACCESS_FINE_LOCATION, check and request should resolve granted without a coordinate fix. A GPS coordinate is a separate concern and may be unavailable in an emulator.\n\n## Evidence\n\nWildLoop's Android E2E run launches with all permissions allowed, then taps the canonical native permission component. The diagnostic screenshot shows the settings escape hatch after the request: https://github.com/stacksjs/wildloop/actions/runs/34693495266/artifacts/10297654245\n\nThe generated Android manifest includes ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION. The native compile matrix succeeds; this is isolated to the runtime permission bridge.\n\nThe failure also prevents cross-platform use of the documented Stacks NativePermissionButton for location permission.