fix(devtools): enable React rendering analysis and fix large trace parsing

[f1shy-dev]

This PR fixes three high-impact gaps surfaced during field testing with React traces: large gz trace parsing caused string overflow errors, summary/capability maps required expensive derived layers, and React render timing lacked classification.

Large trace parsing (src/drivers/devtools.ts)

• Force streaming parse for all .gz files to avoid "Cannot create a string longer than 0x1fffffe8 characters" errors on traces >32MB.

Lazy summary and capability maps (src/drivers/devtools.ts)

• Rewrite buildSummary to compute stats directly from traceEvents instead of pulling derived layers.
• Rewrite buildCapabilityMap to detect capabilities via traceEvents.some instead of materializing dimensions.
• Fix a test that expected summary to fail when devtools/views.framePipeline errored; summary now only depends on devtools/trace.

React render timing (src/drivers/devtools.ts)

• Add normalizeUserTimingName to strip zero-width spaces from React component names.
• Add getRenderMeasureKind to classify measures into component/scheduler/lifecycle/measure based on track.
• Add kind and trackGroup columns to devtools.views.renderMeasures.
• Add test validating React updates appear as scheduler kind, Mount/Unmount as lifecycle, and other Components tracks as component kind.
• Filter devtools.views.renderComponentHotspots and devtools.views.interactionRenders to only include rows with componentName.

Type fix (src/drivers/nextjs-bundle.ts)

• Add explicit type annotation for args parameter in namespace route handler.