feat: add multi-channel options to builds.create

[robingenz]

What

• CreateBuildOptions gains appChannelIds and appChannelNames so a build can be deployed to multiple channels after it succeeds (web only).
• appChannelId is marked deprecated in favor of appChannelIds.
• Type-only change; the request body is passed through unchanged. One passthrough test added.

Requires capawesome-team/cloud-api-worker#793 (deploy the API first).

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR extends the builds.create request options to support deploying a successful web build to multiple channels by introducing appChannelIds and appChannelNames, while deprecating the legacy single-channel appChannelId. It also adds a small passthrough test to confirm the request body includes the new field as expected.

Changes:

• Add appChannelIds?: string[] and appChannelNames?: string[] to CreateBuildOptions (web-only semantics documented).
• Mark CreateBuildOptions.appChannelId as deprecated in favor of appChannelIds.
• Add a resource test verifying appChannelIds is passed through in the POST body (excluding appId).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/resources/builds.ts	Extends build creation options with multi-channel fields and deprecates the single-channel field.
test/resources.test.ts	Adds a passthrough test to ensure appChannelIds is serialized into the request body.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[robingenz]

Closed as not planned for now