feat(types): 为微信小程序云托管服务的 Taro.cloud.callContainer 方法补充 TypeScript 类型定义

[RandallRock123]

这个 PR 做了什么? (简要描述所做更改)

为微信小程序云托管服务的 Taro.cloud.callContainer 方法补充 TypeScript 类型定义，具体添加 config 属性，包含 env 字段用于指定云环境ID。根据微信官方文档规范，确保类型定义与实际API使用方式一致。

参考文档：https://developers.weixin.qq.com/miniprogram/dev/wxcloudservice/wxcloudrun/src/development/call/mini.html

这个 PR 是什么类型? (至少选择一个)

• 错误修复(Bugfix) issue: fix #
• 新功能(Feature)
• 代码重构(Refactor)
• TypeScript 类型定义修改(Typings)
• 文档修改(Docs)
• 代码风格更新(Code style update)
• 其他，请描述(Other, please describe):

这个 PR 涉及以下平台:

• 所有小程序
• 微信小程序
• 支付宝小程序
• 百度小程序
• 字节跳动小程序
• QQ 轻应用
• 京东小程序
• 快应用平台（QuickApp）
• Web 平台（H5）
• 移动端（React-Native）
• 鸿蒙（harmony）

Summary by CodeRabbit

• 新功能
  • 增加了新的云配置选项，用户现可在调用云服务时直接指定环境ID，从而简化操作流程（在已全局配置时无需重复设置）。
• 重构
  • 精简了部分导入操作，进一步优化了API的清晰性和维护性。

[coderabbitai]

"""

Walkthrough

在此次提交中，对 Taro 云函数相关的类型定义进行了更新。主要变化包括将导入语句简化（移除了 DownloadTask 与 UploadTask 的导入），以及在 CallContainerParam 接口中新增了一个可选属性 config，该属性允许直接传入云托管环境标识。更新文件位于 packages/taro/types/api/cloud/index.d.ts。

Changes

文件路径	变更摘要
packages/taro/.../api/cloud/index.d.ts	1. 简化导入语句，移除 DownloadTask 和 UploadTask 导入 2. 在 CallContainerParam 接口中新增可选属性 config?: { env: string; }

Sequence Diagram(s)

sequenceDiagram
    participant 客户端 as 调用者
    participant API as 云函数调用API
    participant 配置 as 配置管理 (Taro.cloud.init)

    客户端->>API: 调用云函数 (传递CallContainerParam，可含config)
    alt config存在
        API->>API: 使用传入的config.env参数
    else config不存在
        API->>配置: 获取初始化配置的环境ID
    end
    API-->>客户端: 返回云函数调用结果

Loading

Poem

我是快乐的小兔子 🐰，
在代码林中跳跃不停，
云函数赋新气，
配置隐现心意，
代码如花开满径！
跳跃中见未来的光明！
"""

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 38c630a and 09a943d.

📒 Files selected for processing (1)

• packages/taro/types/api/cloud/index.d.ts (2 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• packages/taro/types/api/cloud/index.d.ts

⏰ Context from checks skipped due to timeout of 90000ms (6)

• GitHub Check: Build Rust Binding / stable - aarch64-apple-darwin
• GitHub Check: Build Rust Binding / stable - x86_64-unknown-linux-gnu
• GitHub Check: Build Rust Binding / stable - x86_64-unknown-linux-musl
• GitHub Check: Build Rust Binding / stable - x86_64-apple-darwin
• GitHub Check: Build Rust WASM / stable - wasm32-wasi
• GitHub Check: Build Rust Binding / stable - x86_64-pc-windows-msvc

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 57.70%. Comparing base (7d657e6) to head (09a943d).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #17428   +/-   ##
=======================================
  Coverage   57.70%   57.70%           
=======================================
  Files         469      469           
  Lines       26550    26550           
  Branches     5857     5850    -7     
=======================================
  Hits        15320    15320           
- Misses       9729     9767   +38     
+ Partials     1501     1463   -38     

Flag	Coverage Δ
taro-cli	72.37% <ø> (ø)
taro-runtime	59.87% <ø> (ø)
taro-web	49.67% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

see 69 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.