Use trace instead of protocol for lantern

See: #16026

ctrl+f `INTERNAL_LANTERN_USE_TRACE`

There are ~7 tests that produce different results when using the trace instead of the CDP network log. Each one needs to be investigated fully and understood. For the cases where the trace implementation has an error, we need to fix it (Lantern lives in [CDT repo now](https://source.chromium.org/chromium/chromium/src/+/main:third_party/devtools-frontend/src/front_end/models/trace/lantern/)).

[debugNormalizeRequests](https://source.chromium.org/chromium/chromium/src/+/main:third_party/devtools-frontend/src/front_end/models/trace/lantern/graph/PageDependencyGraph.ts;l=425) is critical for debugging the differences.

It's probably not necessary to treat this as a breaking change, but it seems like the safe approach.

Start with issue #16026 and the INTERNAL_LANTERN_USE_TRACE references, then compare the roughly seven differing tests. Use debugNormalizeRequests in PageDependencyGraph.ts and inspect Lantern in the CDT repository to determine whether each difference is expected or an implementation error. Done means the trace path produces correct results for the investigated cases and the switch is safe to adopt.

Written by the indexing model from the issue text.