fix(customrow): only attach BottomTabs custom row to NavigationActivity

[Yoavpagir]

Problem

Owner (Android) crashes during OAuth login. When AppAuth's RedirectUriReceiverActivity (the relay that receives the OAuth redirect) is created, the app dies with:

RuntimeException: Unable to start activity ... RedirectUriReceiverActivity:
IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity.
  at BottomTabsCustomRowAttacher.tryAttach(BottomTabsCustomRowAttacher.kt:96)
  at BottomTabsCustomRowAttacher.onActivityCreated(BottomTabsCustomRowAttacher.kt:55)

Sentry: WIX-ONE-APP-9GFHV — ~5.9k events / 1.6k users, Android-only, still active.

Root cause

BottomTabsCustomRowAttacher is a global Application.ActivityLifecycleCallbacks and runs tryAttach() → findViewById(android.R.id.content) on every activity in the process. For a foreign, non-AppCompat-themed activity (AppAuth's relay), that findViewById forces AppCompatDelegate sub-decor inflation, which requires a Theme.AppCompat and throws. Any third-party non-AppCompat activity (OAuth relays, SDK login flows, etc.) hits this, not just AppAuth.

Fix

Guard the observer to RNN's own NavigationActivity — the only place BottomTabs (and thus the custom row) ever live. Foreign activities are skipped, so findViewById is never called on them.

private fun ensureLayoutObserver(activity: Activity) {
    if (activity !is NavigationActivity) return
    ...
}
private fun tryAttach(activity: Activity) {
    if (activity !is NavigationActivity) return
    ...
}

Verification

Built the playground app with this change and reproduced the exact mechanism on a rooted emulator: launching a non-AppCompat-themed AppCompatActivity into the running process no longer crashes (unpatched: process dies with the stack above). The custom bottom-tabs feature still renders correctly on NavigationActivity — no regression.