fix(tables): show rejected filter errors in the grid and fill imports to the row limit - #9881

Summary

• Table grid now shows the rows-query error instead of an empty table. A filter the server rejects (e.g. 1,000 on a number column with a range operator) used to look identical to "no rows match", because useTable never read the query's error. Only a failed first page shows it; a failed next page or background refetch keeps the loaded rows
• Streaming CSV import now fills the table up to the plan row limit instead of rejecting the whole batch that crosses it. Batches are 5,000 rows, so a file one row over the limit stopped ~4,900 rows short while the error said the table had reached its limit
• When the import stops at the limit, the job fails with how many rows landed (Import stopped at this table's row limit (N rows) on your current plan. M rows were imported; the rest of the file was not.) and persists that count as progress. Appending to a table that is already full still fails with the existing row-limit error and inserts nothing
• No change to the no-rollback design, the sync import path, or TableRowLimitError's wording

Type of Change

• Bug fix

Testing

• lib/table/import-runner.test.ts: 5 new row-limit cases (crossing batch fills to the limit, batch landing exactly on the limit with rows left, append counts existing rows, already-full table inserts nothing, file that exactly fills completes). 4 of them fail against the pre-fix runner, and reverting each new guard (partial-batch slice, imported-count error, progress write before the stop) turns at least one test red
• hooks/use-table.test.ts passes
• biome check on changed files; full type-check, audits and suite left to CI

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (new tests pass the test-audit authoring gate)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)