Collection/binding level alerts #2615
Description
Add support for collection/binding level data movement stalled alerts. Currently we only alert at the task level, meaning if any data is flowing through a capture/materialization, no alert fires - even if specific collections within that task have completely stalled.
This came up with a NetSuite customer who got hit by NetSuite's 2026.1 release bug that updated all transactionlineitem.lastmodifieddates. Their other tables kept flowing normally so no task-level alert fired, but their most critical collection went stale without them knowing.
The broader issue is that customers care about specific tables/collections, not just "any data flowing from the capture." Task-level alerts are too coarse-grained for real use cases like this.