Make homepage carousels fully dynamic, drop brand carousels, dynamic logo/favicon

- Replace the two hardcoded homepage carousels (SpecialSaleCarousel
  pinned to store-specials group 0 only, TopSellingCarousel reading
  from an unrelated plain product query) with StoreSpecialCarousels:
  loops over every group GET /store-specials returns, using each
  group's own title. A new carousel created in the admin panel (e.g.
  the "بهترین‌ها از نگاه شما" one just added) shows up automatically,
  no code change needed.
- Remove the brand-groups integration and its "سامسونگ" carousel
  entirely (getBrandGroups, BrandGroupCarousels) — brand-name
  carousels aren't wanted on this site per explicit instruction.
- SectionTitle's enTitle is now optional, since dynamic store-specials
  groups only have one title string, not a Persian/English pair.
- Move featured categories above the hero-adjacent special carousels
  per the requested homepage order; drop the "دسته‌بندی‌های پرطرفدار"
  heading and its "همه دسته‌ها" button, per request.
- Wire the header/footer logo and the favicon to the real business
  data (logoUrl/logoDarkUrl/faviconUrl from GET business-info) instead
  of static files; removed src/app/favicon.ico, which was silently
  winning over the new dynamic <link rel="icon">.
- CONTEXT.md: document the dynamic-carousel contract and the
  logo/favicon wiring so neither regresses to hardcoded.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

CONTEXT.md

@@ -195,6 +195,50 @@ them in the dashboard; the code path just needs to fall back to whatever the
 `FeaturedCategories.tsx` for the pattern: real slot images when present,
 else the pre-existing UI unchanged).
 
+## Homepage product carousels — fully dynamic, don't hardcode a name/key
+
+`GET /tenants/{domain}/store-specials` returns **every** admin-managed named
+carousel as one flat list — e.g. "Special Sale", "پرفروش‌ها", "بهترین‌ها از
+نگاه شما" all come back from this one call, each with its own `title` and
+`items`. `StoreSpecialCarousels.tsx` maps over the **whole list** (sorted by
+`sortOrder`, empty groups skipped) and renders one titled carousel section
+per group, using `group.title` from the API as the heading — no group
+id/key/title is special-cased in code. This means a brand-new carousel
+created in the Meshkee dashboard (any name) appears on the homepage the next
+time the page renders, with zero code changes.
+
+**Do not**:
+- Hardcode a Persian/English title pair for one of these carousels (that was
+  the old `SpecialSaleCarousel`/`TopSellingCarousel` mistake — two separate
+  components each pinned to one group, with a made-up title instead of the
+  API's own `title`, and `TopSellingCarousel` didn't even read from
+  store-specials, it re-queried the plain product list).
+- Reintroduce a **brand-name carousel** (`GET /website/brand-groups` — used
+  to render a "سامسونگ" section). The user explicitly removed this: brand
+  carousels aren't wanted on this site at all. If similar per-brand curation
+  is wanted later, it should go through admin-managed store-specials groups
+  (a group can be curated by brand already), not a separate brand-groups
+  integration.
+
+`SectionTitle`'s `enTitle` prop is optional for exactly this reason — these
+dynamic groups only have one `title` string from the API, not a Persian/
+English pair, so the small English-caps subtitle just doesn't render for them.
+
+## Branding: logo & favicon are dynamic, not static files
+
+`BusinessInfo` (`getBusinessInfo()`, already fetched in `layout.tsx`) carries
+`logoUrl`, `logoDarkUrl`, `faviconUrl` straight from the API — the same
+values `GET /tenants/{domain}` and `GET .../website/favicon` also expose.
+`Header`'s `Logo` takes a `src` prop (falls back to `public/images/logo.png`
+only if the API value is null) threaded down from `layout.tsx`; `Footer`
+prefers `logoDarkUrl` (falls back to `logoUrl`) since it sits on a dark
+background. The favicon is set via `generateMetadata()`'s `icons` field —
+**there is no `src/app/favicon.ico` file** (deliberately removed): Next.js's
+static-file favicon convention and a dynamic `metadata.icons` entry both
+render a `<link rel="icon">` and browsers aren't guaranteed to prefer the
+second one, so keeping both was silently serving the stale static icon.
+Don't add `app/favicon.ico` (or `public/favicon.ico`) back.
+
 ## Route map
 
 | Route | Notes |