Fix Qibla compass fallback

[escalopa]

What changed

• fall back to the browser Device Orientation API when Telegram orientation tracking is unavailable or relative-only
• request iOS motion/orientation permission directly from the compass button action
• retain the numeric Qibla bearing when no absolute heading is available

Root cause

The Mini App treated Telegram's DeviceOrientation API as the only source of a compass heading. That API is unavailable on older Telegram clients, and Telegram documents that a device may return relative orientation even when absolute data is requested. Both conditions were immediately presented as unsupported.

Validation

• node --check global/internal/adapter/in/miniapp/static/app.js
• git diff --check
• Go package tests are blocked before compilation by the local Go toolchain mismatch: cached/precompiled packages are Go 1.26.3 while the active compiler is Go 1.26.5.