fix: use literal scheme/host in the /open/... deep link intent-filter

android:scheme="@string/deep_linking_scheme"/android:host="@string/deep_linking_host"
compiled fine but never resolved at runtime - confirmed by decoding the actual built
APK's binary manifest, which showed the raw unresolved resource ids
(@7F13034E/@7F13034A) instead of literal values, unlike every sibling intent-filter
in this same manifest (buy-success, request, wc, https), which all use literal
strings and work correctly. PackageManager can't match a <data> scheme/host that
never resolves, so this intent-filter - covering every /open/... deep link,
including the just-added first-signer multisig operation case (PR #14) - has never
been reachable on any real device since it was written, regardless of the
correctness of the Kotlin handling code behind it. Confirmed by attempting the
actual deep link on-device (ADB VIEW intent, unresolved) before finding this.

app/src/main/AndroidManifest.xml

@@ -76,8 +76,8 @@
 
             <intent-filter android:label="@string/app_name">
                 <data
-                    android:host="@string/deep_linking_host"
-                    android:scheme="@string/deep_linking_scheme" />
+                    android:host="pezkuwi"
+                    android:scheme="pezkuwiwallet" />
 
                 <action android:name="android.intent.action.VIEW" />