Add app events to app logs-next - #9100

WHY are these changes introduced?

App Events API records are not yet available through historical CLI retrieval.

WHAT is this pull request doing?

Adds --type app-event and the exact --event-handle filter. Default queries include app events, and the human table displays their event handle under Details and — under Result because these records have no result status.

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

Production validation

• Production tophat — 2026-11-09, tested head b4c3ffdb2813, against billing-event-tophat-oct27.
  • Shared seven-day UTC window: 2026-11-02T17:03:32Z to 2026-11-09T17:03:32Z.
  • --type app-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 was an em dash for every app event.
  • 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.

How to manually test your changes?

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

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

Confirm the event handle appears under Details, Result is —, and JSON preserves the native attributes without adding a synthetic result status.

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