Add backward-compatible scroll type aliases

[yuyutaotao]

Summary

• allow aiScroll's scrollType to accept legacy aliases like once alongside current options
• extend scroll parameter types to advertise the backward-compatible values

Testing

• not run

---

Codex Task

[netlify]

✅ Deploy Preview for midscene ready!

Name	Link
🔨 Latest commit	a266177
🔍 Latest deploy log	https://app.netlify.com/projects/midscene/deploys/69453eb3032f5c0008fdb029
😎 Deploy Preview	https://deploy-preview-1636--midscene.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Legacy scroll aliases still unsupported at runtime

Allowing legacy values in the scroll schema (these enum entries) means YAML flows or direct callActionInActionSpace calls using scrollType: 'once'/'untilBottom' now pass validation, but the platform actions still branch only on the canonical names and throw Unknown scroll event type for anything else (see packages/web-integration/src/web-page.ts lines 494-519 and packages/android/src/device.ts lines 155-183). A script using the newly accepted aliases will therefore fail at runtime instead of performing the intended scroll, so the backward compatibility advertised by this change is not actually achieved.

Useful? React with 👍 / 👎.