Add app billing events to app logs-next - #9101

WHY are these changes introduced?

App billing outcomes are not yet available through historical CLI retrieval.

WHAT is this pull request doing?

Adds --type app-billing-event, reusing the existing --event-handle and --status filters. Default queries include billing events, and the human table shows the event handle and recorded billing outcome.

Part 3 of the six-PR log-type stack, based on #9100. Tracking: EXTLOGS-108.

Validation

• 232 focused tests passed, including native billing-value preservation and table rendering.
• Targeted ESLint, app type-check, CLI bundle, manifest refresh, command snapshot, and diff checks passed.
• Production tophat — 2026-11-09, tested head 9a9de0c3df56, against billing-event-tophat-oct27.
  • Shared seven-day UTC window: 2026-11-02T17:03:32Z to 2026-11-09T17:03:32Z.
  • --type app-billing-event --limit 20: 20 records returned (requested limit reached; this is a sample, not a total). JSON and human commands both exited 0; returned types and timestamps matched the request.
  • Human table: 20 rows, populated Details values, expected headings, and no GraphQL-only API column. Result/status counts matched the native JSON sample.
  • Live exact filters --event-handle: 20 matching records, using values from the returned records; all returned values matched the predicates.
  • Record contents and filter values kept private. No source or service changes. This replaces the earlier production validation notes.
• Prerequisite Rename the App Logs type from WEBHOOK_DELIVERY to WEBHOOK #9098 is merged; the WEBHOOK schema-freshness check now passes.
• Command remains hidden; no changeset for this pre-release stack.

How to manually test your changes?

Using this branch's CLI with access to an app that has recent app billing events:

shopify app logs-next --type app-billing-event --since 1h --limit 5
shopify app logs-next --type app-billing-event --event-handle EVENT_HANDLE --status failure --since 1h --limit 5 --json

Confirm the event handle and recorded result appear in the human table, and JSON preserves native billing fields, including the value as text.

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've considered analytics changes to measure impact
• The change is user-facing — I've identified the correct bump type and added a changeset with pnpm changeset add