RPP: Calculate transferSize natively within ThirdPartyTreeView

The data is from individual ResourceReceivedData, ResourceFinish, etc
instant events. While these are visible (as instant blue events), they
don't display anything by default in the UI. With this setup, the
precise timestamps of when data is received is used. In other words, if
we zoom to only see when a request was sent out, there are 0 bytes
received.

This work puts us one step closer to having a singular implementation
for aggregated selfTime, transferSize, etc grouped by Third Party or
otherwise.

- Taught TraceTree to calculate transferSize
- Mapped *all* trace events comprising a network request to be mapped to an entity, rather than just the syntheticNetworkRequest.
- The EntityMappings of Renderer, Network and the Mapper are now the same.
- The 3P table's numbers match Bottom-up's.
- "Unattributed" is introduced to the 3P table, as by-product of that consistency. However we will reduce it's impact with upcoming work.
- Moved Jack's change for grid node selection triggering hover dimming up to TimelineTreeView, so all TreeViews benefit.
- Allowed the 3P table to use TTV's base onHover method, as no reason to not reuse.

Change-Id: I8ed6b46f9a0ffa09b5e3960b89a8f917a33e3948
Bug: 388458798
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/6220264
Reviewed-by: Adriana Ixba <aixba@chromium.org>
Commit-Queue: Paul Irish <paulirish@chromium.org>
Auto-Submit: Paul Irish <paulirish@chromium.org>