feat(event): support drive namespace events in event consume (drive.notice.comment_add_v1)

Problem

lark-cli event consume only exposes board / card / im / minutes / task / vc EventKeys. The entire drive namespace is missing — verified on v1.0.68:

$ lark-cli event consume drive.notice.comment_add_v1 --as bot
{"ok":false,"error":{"type":"validation","message":"unknown EventKey: drive.notice.comment_add_v1"}}

The server side is already fully open, which makes this gap surprising:

• drive user subscription (scope docs:event:subscribe) succeeds per-file: ok:true
• Comments REST (list / reply / resolve) all work under bot identity
• Only the consume surface is missing, so bots are forced to poll.

Use case: doc comments as durable, anchored feedback on agent-generated documents (e.g. daily paper digests delivered as docx; user comments on specific entries; bot harvests them into a feedback pipeline, replies and resolves). A natural agent-feedback loop that every doc-producing bot will want.

Why CLI support is the only clean path: apps built on the CLI event bus daemon cannot safely run a side-car SDK WebSocket consumer for the missing keys — events are load-balanced across an app's long connections, so a second consumer steals events from the daemon. The daemon is exactly the right place for this key.

Ask: add drive.notice.comment_add_v1 (ideally the drive event family) to the consumable EventKeys.

Environment: lark-cli 1.0.68, macOS

Start at the lark-cli event consume entry point and trace how its supported EventKeys are defined and validated. Add drive.notice.comment_add_v1 to the consumable keys, then verify that the command accepts it instead of returning an unknown EventKey validation error.