feat: add total count to search responses

[eemmiillyy]

This PR adds the totalCount field to search responses (search,search.byTable, search.all, and vectorSearch)

It contains breaking changes to the search APIs as the response is no longer an array, but an object, for example:

{ records: [], totalCount: 1 }

Note that: search.byTable returns a records object rather than an records array. Each table name is a key pointing to an array, for example:

{ records: { users: [], posts: [] }, totalCount: 1 }

Resolves #1081

[changeset-bot]

🦋 Changeset detected

Latest commit: ffcf6cb

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 10 packages

Name	Type
@xata.io/client	Minor
@xata.io/cli	Patch
@xata.io/codegen	Minor
@xata.io/importer	Patch
@xata.io/plugin-client-cache	Patch
@xata.io/plugin-client-cloudflare	Patch
@xata.io/drizzle	Patch
@xata.io/kysely	Patch
@xata.io/netlify	Patch
@xata.io/plugin-client-opentelemetry	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[github-actions]

size-limit report 📦

Path	Size
packages/client/dist/index.mjs	17.97 KB (+0.22% 🔺)
packages/client/dist/index.cjs	19.32 KB (+0.23% 🔺)
packages/codegen/dist/index.mjs	2.58 MB (+0.01% 🔺)
packages/codegen/dist/index.cjs	2.58 MB (+0.01% 🔺)

[github-actions]

Your pull request has been published to npm.

You can install @xata.io/client by running:

npm install @xata.io/[email protected]

Other packages are published like this:

npm install @xata.io/[email protected]

To test the CLI, run:

npx @xata.io/[email protected]

[SferaDev]

I'll fully review it on Thursday when I'm back. Only concern is in byTable what happens if I have a table called totalCount?

[eemmiillyy]

@SferaDev Yeah that's a good point, I've now nested under records: {...} to avoid this edge case