refactor: restructure navigation into 5 grouped hubs, off the 22-item flat strip

Implements the researched IA fix: mobile nav UX consensus caps primary
destinations at 4-5 (uxpin.com, fintech/banking 2026 UX research), and
this app had grown to 22 tabs in one horizontally-scrolling row —
exactly the anti-pattern that research flags for choice paralysis and
slower task completion.

New structure — 5 bottom-nav hubs, grouped by what the user is actually
trying to do, not build order:
- Home: Coverage (unchanged, still the landing screen)
- Estate: Assets, Faraid, Insurance, Wassiyah, Hibah, Family Waqf,
  Nominate, Claims (H2)
- Giving: Zakat, Sadaqah, Khairat
- Family: Tree, Trigger, Mutawalli, Manage (was 'Family', renamed to
  avoid colliding with the hub's own label), Neighbourhood
- Daily: Prayer Times, Qibla, Quran, Locate

Each hub reveals its own sub-nav one tap in, instead of every tab
competing for space in a single row. Settings moved out of the tab
strip entirely into a header gear icon, matching the banking-app pattern
of keeping settings out of primary thumb-reach real estate. The bottom
nav is now fixed (thumb-zone), sub-nav keeps the old sticky-top position.

Cross-component navigation (nav.js requestedTab, used by the Family
Tree's 'give sadaqah in memory' link) now resolves a tab label to its
owning (hub, sub-tab) pair instead of a flat index — verified live.

This touches every E2E suite: a single click on a tab's old selector no
longer reaches it (hub, then sub-tab). Added a shared gotoTab(page, label)
helper to e2e-auth-helper.cjs encapsulating the two-step navigation, and
migrated all ~22 affected test files off direct nav-button selectors —
mechanical substitution followed by manual fixes for local clickTab
wrappers, template-literal selectors, and active-state assertions that
needed to target the new .hub-tab/.subnav structure specifically.

Full regression after migration: every suite passes (one isolated
Family Tree flake confirmed clean on rerun, unrelated to navigation).

e2e-family-tree.cjs

@@ -6,7 +6,7 @@
 // proven for Wassiyah/Waqf).
 const { chromium } = require('playwright');
 const path = require('path');
-const { signInFreshFamily } = require('./e2e-auth-helper.cjs');
+const { signInFreshFamily, gotoTab } = require('./e2e-auth-helper.cjs');
 const BASE = 'https://moslem04.falahos.my/';
 const results = [];
 const consoleErrors = [];
@@ -19,7 +19,7 @@ async function main() {
   page.on('pageerror', e => consoleErrors.push(e.message));
 
   const familyName = await signInFreshFamily(page, BASE, 'e2e-family-tree');
-  await page.locator('nav button[aria-label="Tree"]').click();
+  await gotoTab(page, 'Tree');
   await page.waitForTimeout(600);
 
   // Add three people: grandfather, father, son
@@ -109,7 +109,7 @@ async function main() {
   // ── Isolation: a fresh family (same account) should NOT see this tree ──
   const isolationPage = await browser.newPage({ viewport: { width: 390, height: 844 } });
   await signInFreshFamily(isolationPage, BASE, 'e2e-family-tree-isolation');
-  await isolationPage.locator('nav button[aria-label="Tree"]').click();
+  await gotoTab(isolationPage, 'Tree');
   await isolationPage.waitForTimeout(600);
   const leakedPerson = await isolationPage.locator('.person-card', { hasText: 'Grandfather Ahmad' }).isVisible().catch(() => false);
   record('Family Tree: a different family sees none of this tree (isolation)', !leakedPerson);