fix download url request not encode space

[mmyduckx]

Re: #https://github.com/cocos/3d-tasks/issues/7874

Changelog

---

Continuous Integration

This pull request:

• needs automatic test cases check.

  Manual trigger with @cocos-robot run test cases afterward.

• does not change any runtime related code or build configuration

  If any reviewer thinks the CI checks are needed, please uncheck this option, then close and reopen the issue.

---

Compatibility Check

This pull request:

• changes public API, and have ensured backward compatibility with deprecated features.
• affects platform compatibility, e.g. system version, browser version, platform sdk version, platform toolchain, language version, hardware compatibility etc.
• affects file structure of the build package or build configuration which requires user project upgrade.
• introduces breaking changes, please list all changes, affected features and the scope of violation.

[github-actions]

Interface Check Report

! WARNING this pull request has changed these public interfaces:

@@ -30194,9 +30194,11 @@
             constructor(hints: DownloaderHints);
             /**
              * @en create a download task. The maximum size for a single download file is 4GB.
              * @zh 创建一个下载任务. 单个下载文件最大为4GB.
-             * @param requestURL @en Request download resource URL  @zh 请求下载资源的URL
+             * @param requestURL
+             * @en Request download resource URL. Node: Users need to encode the URL containing special characters except spaces (such as Chinese, etc.)
+             * @zh 请求下载资源的URL. 注意: 当URL中包含除空格外特殊字符(如:中文等)时需要用户自行编码后传入.
              * @param storagePath @en Storage path for downloaded file @zh 下载文件存储路径
              * @param identifier  @en identifier @zh 标识符
              * @return @en DownloaderTask @zh 下载任务对象
              * @example
@@ -30253,9 +30255,11 @@
             /**
              * @deprecated since v3.6.0, please use `createDownloadTask` to instead.
              * @en create a download task. The maximum size for a single download file is 4GB.
              * @zh 创建一个下载任务. 单个下载文件最大为4GB.
-             * @param requestURL @en Request download resource URL  @zh 请求下载资源的URL
+             * @param requestURL
+             * @en Request download resource URL. Node: Users need to encode the URL containing special characters except spaces (such as Chinese, etc.)
+             * @zh 请求下载资源的URL. 注意: 当URL中包含除空格外特殊字符(如:中文等)时需要用户自行编码后传入.
              * @param storagePath @en Storage path for downloaded file @zh 下载文件存储路径
              * @param identifier  @en identifier @zh 标识符
              * @return @en DownloaderTask @zh 下载任务对象
              * @example

[PatriceJiang]

Should we implement url_encode ?

[minggo]

As discussed, may let developers encode the url if needed.

[mmyduckx]

Should we implement url_encode ?

In native, the encoding methods in different platforms are not consistent. Eg, Windows needs locate some last of char like /to substr the string and then call curl_easy_escape(), which will affect the performance when deal with amount of requests, And another potential problem is that if it is a POST request, which may be very long and cotains special char after /, the position of this substr is not accurate. so I think developer do the encoding if needed is a better approach.

[minggo]

It is better to provide a function to encode the string.

[mmyduckx]

It is better to provide a function to encode the string.

We can't predict the url request pass in from the user. Eg:it may be an http resource request(in this case we can find last of '/' to encode) or a very long POST request with special characters (in this case, user must locate and encode the POST parameters separately, otherwise an error will occur). So different urls need to encode in different way, and the engine cannot encode uniformly. The better approach is to let the user do encoding before passing in.

[minggo]

What i mean is to encode the space, as did in the PR.