修复picker-view-column在taro4不生效

[HappyYA]

这个 PR 做了什么？ (简要描述所做更改)
问题是在删除基类模版中block后出现的。
根据issues中ycyeye说的方法做了修改。
辛苦看一下是否有问题，没问题尽快合并，着急用谢谢。

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

• 错误修复 (Bugfix) issue: fix picker-view-column在taro4不生效（同样的代码微信正常） #17460
• 新功能 (Feature)
• 代码重构 (Refactor)
• TypeScript 类型定义修改 (Types)
• 文档修改 (Docs)
• 代码风格更新 (Code style update)
• 构建优化 (Chore)
• 其他，请描述 (Other, please describe):

这个 PR 涉及以下平台：

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

Summary by CodeRabbit

• 修复
  • 优化了 picker-view 相关节点的处理逻辑，提升了模板渲染的一致性和准确性。
  • 现在 picker-view-column 节点的模板内容将正常显示，不再被隐藏。

[coderabbitai]

"""

Walkthrough

本次更改简化了 modifyLoopBody 方法，移除了针对 picker-view 节点的特殊处理逻辑，现在无论节点名称如何，均直接返回子内容。同时，modifyTemplateResult 方法调整为仅对 swiper-item 节点返回空字符串，picker-view-column 节点将正常返回模板结果。

Changes

文件/文件组	变更摘要
packages/taro-platform-alipay/src/template.ts	简化 modifyLoopBody，移除 picker-view 特殊处理。调整 modifyTemplateResult，仅对 swiper-item 返回空字符串，picker-view-column 节点正常渲染。

Sequence Diagram(s)

sequenceDiagram
    participant App
    participant TemplateEngine

    App->>TemplateEngine: 渲染 picker-view 结构
    TemplateEngine->>TemplateEngine: 调用 modifyLoopBody (直接返回子内容)
    TemplateEngine->>TemplateEngine: 调用 modifyTemplateResult
    alt 节点为 swiper-item
        TemplateEngine-->>App: 返回空字符串
    else 其他节点（如 picker-view-column）
        TemplateEngine-->>App: 返回原始模板结果
    end

Loading

Assessment against linked issues

Objective	Addressed	Explanation
picker-view-column 正常渲染于支付宝小程序（#17460）	✅

Assessment against linked issues: Out-of-scope changes

（未发现与已链接 issue 目标无关的代码更改）

Suggested reviewers

• tutuxxx

Poem

小兔敲键盘，模板轻轻改，
picker-view-column，终于能盛开。
旧逻辑已走远，新渲染常在，
支付宝小程序，界面更精彩！
🐇✨
"""

---

📜 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 1c7d6cb and 908af1a.

📒 Files selected for processing (1)

• packages/taro-platform-alipay/src/template.ts (2 hunks)

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

• packages/taro-platform-alipay/src/template.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-musl
• GitHub Check: Build Rust Binding / stable - x86_64-pc-windows-msvc
• GitHub Check: Build Rust Binding / stable - x86_64-unknown-linux-gnu
• GitHub Check: Build Rust Binding / stable - x86_64-apple-darwin
• GitHub Check: Build Rust WASM / stable - wasm32-wasi

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment

---

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.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 explain its main purpose.
  • @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 auto-generate unit tests to generate unit tests for 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 55.90%. Comparing base (1f097d5) to head (908af1a).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff            @@
##             main   #17884    +/-   ##
========================================
  Coverage   55.90%   55.90%            
========================================
  Files         417      417            
  Lines       21693    21693            
  Branches     5385     5352    -33     
========================================
  Hits        12127    12127            
- Misses       7930     8061   +131     
+ Partials     1636     1505   -131     

Flag	Coverage Δ
taro-cli	72.42% <ø> (ø)
taro-runtime	59.87% <ø> (ø)
taro-web	53.19% <ø> (ø)

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

see 42 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.