Fix failing test from conflicting changes in last two commits

Bug: none
Change-Id: I46cff341094f8854f403038d98109758ae0c3e52
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6714943
Auto-Submit: Connor Clark <[email protected]>
Reviewed-by: Paul Irish <[email protected]>
Commit-Queue: Connor Clark <[email protected]>

Author: Connor Clark

front_end/models/ai_assistance/data_formatters/PerformanceInsightFormatter.test.ts

@@ -102,9 +102,10 @@ We can break this time down into the 2 phases that combine to make the LCP time:
     const {parsedTrace, insights} = await TraceLoader.traceEngine(this, 'dpr.json.gz');
     assert.isOk(insights);
     const firstNav = getFirstOrError(parsedTrace.Meta.navigationsByNavigationId.values());
+    const insightSet = getInsightSetOrError(insights, firstNav);
     const insight = getInsightOrError('LCPBreakdown', insights, firstNav);
 
-    const formatter = new PerformanceInsightFormatter(new ActiveInsight(insight, parsedTrace));
+    const formatter = new PerformanceInsightFormatter(new ActiveInsight(insight, insightSet.bounds, parsedTrace));
     const output = formatter.formatInsight().split('Timings:')[0];
     const expected = `## Insight Title: LCP breakdown