Feature Request: Virtualized listing for directory contents

[mechite]

This request is related to #2615 which was created in Oct 2020.
Notes from the related issue discussion:

• As of Mar 9, 2025, the following diff to FileManagerContainer was effective for a "bug" that was discussed.
  Files were sorted post-truncation to the 250 file limit, leading to incorrect sorting.
  This patch assumes that the sorting function is not an expensive call, over a large directory.

-                                 {sortFiles(files.slice(0, 250)).map((file) => (
+                                {sortFiles(files).slice(0, 250).map((file) => (

This was considered a "bug" due to the following text, as of the writing of those comments:

• @DaneEveritt proposed a virtualized listing setup. This is the best final solution to this issue.
  Other people in the discussion proposed/repeated that limits should be configurable.

• @mechite (me) proposed writing a PR to implement this.
  As of time of writing, PRs from people outside of core project team were said to 'not be accepted'.
  I now withdraw my offering as I currently do not have the resources and this issue was raised a while ago.
  If maintainers approve this discussion, someone else can feel free to assume this position if they desire.

[DaneEveritt]

We also need to account for paginated API responses from Wings (proxied through the Panel) for this. You wouldn't want to send 10k files over the wire, that is unnecessarily slow and extremely expensive to do. The virtual list would also need to handle requesting additional resources as it reaches the bottom.