[Feature Request] Dev Tools Callback Graph per Page

The recent introduction of hide_all_callbacks and the hidden flag for both server-side and client-side callbacks has made the Dev Tools callback graph genuinely useful for large, multi-page Dash apps. Huge kudos to @l0uden and @CNFeffery for these improvements 🚀

That said, for dashboards with dozens of pages, the callback graph still becomes overwhelming because it aggregates callbacks from all pages at once. It would be incredibly helpful to have an option to display only the callbacks relevant to the currently active page.

I understand this may be non-trivial (or even impossible) to implement especially given shared callbacks, dynamic layouts, or cross-page dependencies. But if feasible, such a thing would dramatically improve usability and debugging productivity for complex multi-page applications.

The issue does not name files, tests, or entry points; start by locating the Dev Tools callback-graph implementation and its page or callback metadata. Done means an option can show only callbacks relevant to the active page while accounting for shared callbacks, dynamic layouts, and cross-page dependencies.