fix(upload): resolve 100-entry limit of readEntries in Chrome

[DragonMK3]

Description / 描述

This PR implements a recursive loop for dirReader.readEntries() within the traverseFileTree function in the file src/papges/home/uploads/utils.ts. This ensures that all entries in a directory are retrieved, not just the first batch.

Motivation and Context / 背景

In Chromium-based browsers (Chrome, Edge), the FileSystemDirectoryReader.readEntries() API typically returns a maximum of 100 entries per call. Previously, uploading a folder with more than 100 files would result in only the first 100 files being processed, causing data loss. This change calls readEntries repeatedly until an empty array is returned, ensuring complete folder traversal regardless of the file count.

How Has This Been Tested? / 测试

1. Create a folder containing 512 empty text file.
2. Dragged and dropped the folder into the upload area.
3. Verified that the console/UI correctly identified all 512 files, whereas previously it stopped at 100 around.

Checklist / 检查清单

• I have read the CONTRIBUTING document.
  我已阅读 CONTRIBUTING 文档。
• I have formatted my code with go fmt or prettier.
  我已使用 go fmt 或 prettier 格式化提交的代码。
• I have added appropriate labels to this PR (or mentioned needed labels in the description if lacking permissions).
  我已为此 PR 添加了适当的标签（如无权限或需要的标签不存在，请在描述中说明，管理员将后续处理）。
• I have requested review from relevant code authors using the "Request review" feature when applicable.
  我已在适当情况下使用"Request review"功能请求相关代码作者进行审查。
• I have updated the repository accordingly (If it’s needed).
  我已相应更新了相关仓库（若适用）。
  • OpenList-Frontend #XXXX
  • OpenList-Docs #XXXX