feat: Add lazy panel loading support

[jakduch]

Summary

Implements lazy loading for debug bar panels (resolves #530). Panels registered with lazy: true have their getPanel() deferred to a shutdown function — the tab is rendered immediately, but the panel content is stored in the session and fetched via AJAX when the user clicks or hovers over the tab.

This is useful for panels that perform expensive operations (database profiling, API call logging, heavy data analysis) — they no longer slow down the page response time.

Usage

// Normal panel (eager) — rendered during the request
Debugger::getBar()->addPanel(new MyPanel, 'my-panel');

// Lazy panel — getPanel() is called in shutdown, content served via AJAX
Debugger::getBar()->addPanel(new MyExpensivePanel, 'my-panel', lazy: true);

How it works

1. Bar::addPanel() accepts a new lazy: bool = false parameter
2. During renderPanels(), lazy panels skip getPanel() — only getTab() is called
3. After the response is sent, renderLazyPanels() calls getPanel() and stores content in session via DeferredContent
4. A new AJAX endpoint (_tracy_bar=lazy-panel.{requestId}.{panelId}) serves the panel content as JSON
5. On the client side, bar.js detects data-tracy-lazy panels and fetches content on first interaction

Changes

• Bar.php — addPanel() with lazy param, renderLazyPanels() method, lazy-aware renderPanels()
• DeferredContent.php — New lazy-panel AJAX endpoint
• bar.js — fetchLazyContent() method, lazy-aware Panel.init()
• bar.phtml — Lazy panels get clickable <a> tabs
• panels.phtml — Lazy panels get data-tracy-lazy="1" attribute
• DevelopmentStrategy.php — Calls renderLazyPanels() after render()
• ProductionStrategy.php — Matching interface update

Demo

A demo page is included at examples/lazy-panels.php with three panels: one eager and two lazy (simulating expensive operations with usleep).

Backward compatibility

Fully backward compatible — the lazy parameter defaults to false, so existing addPanel() calls work unchanged. No changes to IBarPanel interface.

[jakduch]

@dg thanks for the 👍!

I've merged current master into the branch and resolved the conflicts. It needed a bit of rework since the Bar frontend moved to Shadow DOM and the templates were reworked, so the lazy loading is now re-applied on top of the new architecture. The PR is conflict-free and mergeable again.

A couple of questions:

• Would you like me to keep it up to date with master going forward?
• Is landing lazy panel loading something you'd want to include in Tracy?
• Anything you'd like me to add or change to make it merge-ready (tests, docs, API tweaks)?

Happy to take it whatever direction works best for you.