feat: add error tracking and retry methods to query collection utils

[lucasweng]

Summary

• Add lastError, isError, errorCount and clearError methods to query collection utils per Enhanced Error Handling and Reporting for query-db-collection #347
• Add new tests to verify error state tracking, ensure clearError triggers a refetch, and collection operations function as expected with cached data while in an error state.

Note: To keep the diff focused, this PR does not implement onError, onSettled, and useErrorBoundary. These will be addressed in a separate PR.

Test Plan

• Tests pass locally
• Package builds successfully

[pkg-pr-new]

More templates

• tanstack-start-db-projects-example
• @tanstack/db-example-react-todo
• @tanstack/db-example-solid-todo

@tanstack/db

npm i https://pkg.pr.new/@tanstack/db@441

@tanstack/db-ivm

npm i https://pkg.pr.new/@tanstack/db-ivm@441

@tanstack/electric-db-collection

npm i https://pkg.pr.new/@tanstack/electric-db-collection@441

@tanstack/query-db-collection

npm i https://pkg.pr.new/@tanstack/query-db-collection@441

@tanstack/react-db

npm i https://pkg.pr.new/@tanstack/react-db@441

@tanstack/solid-db

npm i https://pkg.pr.new/@tanstack/solid-db@441

@tanstack/svelte-db

npm i https://pkg.pr.new/@tanstack/svelte-db@441

@tanstack/trailbase-db-collection

npm i https://pkg.pr.new/@tanstack/trailbase-db-collection@441

@tanstack/vue-db

npm i https://pkg.pr.new/@tanstack/vue-db@441

commit: a7cf838

[KyleAMathews]

ChatGPT's review https://chatgpt.com/share/68add190-8f64-800c-bc40-1218ca9d9e7f

[changeset-bot]

🦋 Changeset detected

Latest commit: a7cf838

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

This PR includes changesets to release 1 package

Name	Type
@tanstack/query-db-collection	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

[lucasweng]

ChatGPT's review https://chatgpt.com/share/68add190-8f64-800c-bc40-1218ca9d9e7f

Thanks @KyleAMathews. I updated the error tracking logic and added a retry test in a7cf838 per the review.

I didn't adopt the suggestion to have clearError throw on refetch failure though. The method's contract is to reset the error state, and throwing an exception could make it appear that the error state wasn't successfully cleared when it actually was, which may confuse users. If callers need to handle refetch failures, they can check the errorCount or isError state after calling clearError. Would like to know your thoughts on this 🙏