refactor: rename marketplace to storefront across the entire monorepo

Comprehensive rename of all marketplace references to storefront:
- API module: apps/api/src/modules/marketplace/ → storefront/
- Components: MarketplaceHeader → StorefrontHeader, MarketplaceShell →
  StorefrontShell, MarketplaceFooter → StorefrontFooter
- Types: marketplace-homepage.ts → storefront-homepage.ts
- Test files: employee-marketplace-* → employee-storefront-*
- All source code identifiers, imports, route paths, and strings
- Documentation (docs/), CI config (.gitlab-ci.yml), scripts
- Dashboard, admin, storefront workspace references
- Prisma field names preserved (isListedOnMarketplace, marketplaceRating,
  marketplaceFunnelEvent) as they map to database schema

Validation:
- API type-check: 0 errors
- Storefront type-check: 0 errors
- Dashboard type-check: 0 errors
- Full monorepo type-check: only pre-existing admin TS18046

docs/DOCKER.md

@@ -20,7 +20,7 @@ docker compose -f docker-compose.dev.yml --profile full up --build
 
 Services:
 
-- marketplace: `http://localhost:3000`
+- storefront: `http://localhost:3000`
 - dashboard: `http://localhost:3000/dashboard`
 - admin: `http://localhost:3000/admin`
 - public-site: `http://localhost:3003`
@@ -31,12 +31,12 @@ Each dev app now runs in its own container and can be started independently with
 
 ```bash
 docker compose -f docker-compose.dev.yml --profile api up --build
-docker compose -f docker-compose.dev.yml --profile marketplace up --build
+docker compose -f docker-compose.dev.yml --profile storefront up --build
 docker compose -f docker-compose.dev.yml --profile dashboard up --build
 docker compose -f docker-compose.dev.yml --profile admin up --build
 docker compose -f docker-compose.dev.yml --profile public-site up --build
 docker compose -f docker-compose.dev.yml --profile tools up --build
-docker compose -f docker-compose.dev.yml --profile api --profile marketplace --profile dashboard --profile admin up --build
+docker compose -f docker-compose.dev.yml --profile api --profile storefront --profile dashboard --profile admin up --build
 ```
 
 Notes:
@@ -121,7 +121,7 @@ Add an A record for every subdomain to your server's public IP before deploying
 
 | Subdomain | Service |
 |---|---|
-| `rentaldrivego.ma` | marketplace and public site |
+| `rentaldrivego.ma` | storefront and public site |
 | `api.rentaldrivego.ma` | API |
 | `pgmanage.rentaldrivego.ma` | pgManage (DB admin) |
 | `portainer.rentaldrivego.ma` | Portainer |
@@ -163,7 +163,7 @@ Open `.env.docker.production` and fill in every value. The minimum required secr
 
 Production now derives `DATABASE_URL` inside the app container from `POSTGRES_HOST`, `POSTGRES_PORT`, `POSTGRES_DB`, `POSTGRES_USER`, and `POSTGRES_PASSWORD` when `DATABASE_URL_FROM_POSTGRES=true`. That avoids Prisma auth failures when the database password contains reserved URL characters such as `@`, `:`, or `/`.
 
-The example file uses `rentaldrivego.ma` for the marketplace and public site. The dashboard and admin panel are routed under that same host at `/dashboard` and `/admin`.
+The example file uses `rentaldrivego.ma` for the storefront and public site. The dashboard and admin panel are routed under that same host at `/dashboard` and `/admin`.
 Set `PORTAINER_DOMAIN=portainer.rentaldrivego.ma` in `.env.docker.production` to expose Portainer through Traefik.
 Set `PGMANAGE_DOMAIN=pgmanage.rentaldrivego.ma` to expose pgManage through Traefik, and set `PGMANAGE_LICENSE_KEY` if you are running the enterprise image.
 Set `REGISTRY_DOMAIN=registry.rentaldrivego.ma` to expose the Docker registry through Traefik.
@@ -255,7 +255,7 @@ npm run docker:prod:start:traefik
 npm run docker:prod:start:postgres
 npm run docker:prod:start:redis
 npm run docker:prod:start:api
-npm run docker:prod:start:marketplace
+npm run docker:prod:start:storefront
 npm run docker:prod:start:dashboard
 npm run docker:prod:start:admin
 npm run docker:prod:start:frontends
@@ -268,7 +268,7 @@ npm run docker:prod:start:api && npm run docker:prod:start:frontends
 
 Docker will:
 1. Build the monorepo image on the server
-2. Start all app services (`api`, `marketplace`, `dashboard`, `admin`, `pgmanage`)
+2. Start all app services (`api`, `storefront`, `dashboard`, `admin`, `pgmanage`)
 
 Traefik automatically picks up the containers and provisions TLS certificates. Services are live at their `https://` URLs within ~30 seconds.