feat(admin-search)!: add baseFilter to scope search results per request

[jhb-dev]

What

Adds a baseFilter option (({ req }) => Where | Promise<Where>) that restricts search results to a constraint resolved against the current request. The filter runs on the server and is combined with the typed query using and, so results stay in scope even before anything is typed.

The main use is multi-tenancy: scoping the search to the tenant selected in the admin panel.

adminSearchPlugin({
  baseFilter: ({ req }) => {
    const tenant = getTenantFromCookie(req.headers, req.payload.db.defaultIDType)
    return tenant ? { tenant: { equals: tenant } } : {}
  },
})

This scopes what the search offers, not what the API permits — it is not access control. The README points at searchOverrides.access.read for constraining GET /api/search server-side.

BREAKING

The header component is now a server component so it can evaluate baseFilter before rendering. It moved:

• @jhb.software/payload-admin-search/client#SearchWrapper → @jhb.software/payload-admin-search/rsc#SearchWrapper
• the /client export now provides SearchWrapperClient in place of SearchWrapper

Consumers must run payload generate:importmap after upgrading, otherwise the search component resolves to nothing and disappears from the admin header.

Per the repo's breaking-change policy this is a minor bump (plugin is pre-1.0).

Tests

• src/components/SearchWrapper/resolveBaseFilter.test.ts
• src/components/SearchModal/buildSearchQuery.test.ts — the base filter and the typed query are combined with and

Vitest is newly configured for this plugin (vitest.config.ts).

Dev app demonstration

dev/ gains a tenants collection, multi-tenant plugin wiring in dev/src/payload.config.ts, a baseFilter example in the plugin invocation, and seeded per-tenant documents. Switching tenants in the admin panel changes what the search returns.