Add --name and --payload-max-bytes to appduct events tail and since

[V3RON]

Part of #94

Why

appduct events tail and appduct events since have no name filter or payload cap, although the daemon supports both after the earlier slices of #94. A script can't tell from the events since output whether events were evicted or more pages remain.

Expected outcome

• appduct events tail [selector] [--name <glob>] [--payload-max-bytes <n>]
• appduct events since [selector] <cursor> [--name <glob>] [--payload-max-bytes <n>]
• Both flags pass straight through to events.subscribe and events.since. Neither has a default, so nothing is truncated unless asked.
• The trailing cursor line of events since prints { cursor, dropped, remaining } under --json, and cursor: 12, dropped: 0, remaining: 40 (run "appduct events since 12" to resume from here) otherwise, keeping today's resume hint.
• The CLI reference and help list the new flags under both verbs.

Constraints and non-goals

• Builds on the noun-verb CLI from feat(cli): unify the CLI as noun-verb commands (#96) #111.
• No other CLI changes.

How we know it is done

1. appduct events tail --name '*_failed' --json prints only matching NDJSON lines.
2. appduct events since 0 --name '*_failed' --json prints only matching NDJSON lines.
3. The events since cursor line carries dropped and remaining, in both --json and human output.
4. appduct events tail --json and appduct events since 0 --json do not truncate payloads without --payload-max-bytes, and truncate with it.

Alternatives considered

See #94.