storage root lists all files flattened (empty `path` param sent to backend)

[alexzandermatveev]

Environment

• OpenList v4.2.6 (docker image openlistteam/openlist:latest)
• Driver: Teldrive
• Backend: Teldrive v1.8.3 (tgdrive/teldrive)

Describe the bug
Listing the storage root of a Teldrive storage shows the user's entire file tree
flattened in one list instead of the actual root directory children. Navigating
into subdirectories works correctly.

Root cause
For the storage root the driver issues GET /api/files without a path query
parameter (the root dir object's GetPath() returns an empty string). Teldrive
treats a missing/empty path as "no path filter" and returns every user file:

• GET /api/files?path=/ -> correct root children (2 items)
• GET /api/files -> ALL user files flattened (54 items)
• GET /api/files?path=/oldDisk -> correct children (11 items)

Additionally, setting "Root folder path" (root_folder_path) on the storage has
no effect: the Teldrive driver never reads d.RootPath.

Steps to reproduce

1. Add a Teldrive storage (url + access_token cookie).
2. Open the storage root in the web UI -> all files are shown flattened.
3. Open any subfolder -> listing is correct.

Expected behavior
The storage root should list the Teldrive root directory (i.e. request with
path=/).

Suggested fix
In drivers/teldrive/driver.go, List():

p := dir.GetPath()
if p == "" {
    p = "/"
}

and use p in the query params of both the first page request and the
pagination requests. Optionally honor d.RootPath to allow mounting a subfolder
as the storage root.

Side note for upstream Teldrive (tgdrive/teldrive): /api/files currently
returns the whole user tree when path is missing/empty instead of rejecting
the request - it might be worth requiring the parameter there as well.

[github-actions]

⚠️ 你的 Issue 不符合提交规则。请先阅读相关规范后再重新提交。当前 Issue 将被自动关闭并锁定。如需继续提交，请确认已了解规则后创建新的 Issue。
⚠️ Your issue does not comply with the submission rules. Please read the guidelines before submitting again. This issue will be automatically closed and locked. If you wish to proceed, please confirm that you have reviewed the rules before creating a new issue.