When the data browsing webview is opened, run a find to fetch documents from the collection. This should have a cancel button and use abort controllers to cancel the operation. Add pagination actions, the refresh button, and show the pagination document count. When the webview is closed, cancel any ongoing operations. Ensure we surface errors to the users. 

When the request for the documents and the count are in progress we show loaders (and a cancel button in the find). Let's have the requests run in parallel, but not wait for both to complete before returning the respective response. We'd like these two to be independent in their responses, so the user isn't waiting for both to finish when they are only interested in the results of one request. 

Instead of showing a count of zero for time series and views we should show an N/A with a tooltip that says that we don't run a count for those collections.

We'll also want a zero state (no documents).

We are not yet adding the sort or the select for documents to show count. We also aren't making the documents appear in a nice way or adding the document actions, those are linked tickets. No insert document yet.
Use VSCode elements vscode-elements package wherever possible for components.

Designs:

https://www.figma.com/design/QE0mDJK9hlbPK9shnQCIbG/VS-CODE--DATA-BROWSING?node-id=1749-175007&t=FgOGFa4NEDo4prqy-4 

If we need to have a state management system, we use redux for state management, otherwise let's keep things simple in react hooks/context. The data-modeling store in Compass is a good place to follow for patterns (without Compass specific parts): https://github.com/mongodb-js/compass/blob/main/packages/compass-data-modeling/src/store/index.ts