ADPF: report different actual duration for frames with throttled swaps

The current logic includes the time spent waiting due to a throttled
swap in the ADPF actual duration report, so the system thinks that the
app needs more CPU resources and increases power consumption when it's
not actually helpful. Examples include playing a 30fps video on some
devices - see the linked bug for more details.

The new reporting logic (disabled by default, controlled by
`EnableADPFIgnoreThrottledTime`) excludes the time between "Swap
throttled" and the next `ScheduleBeginFrameDeadline` from the reported
actual duration.

Bug: 469586679
Change-Id: I7e23b9fa938820fdbaa5474faae42f8026abc980
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7531995
Commit-Queue: Igor Kraskevich <kraskevich@google.com>
Reviewed-by: Jonathan Ross <jonross@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1580121}
NOKEYCHECK=True
GitOrigin-RevId: 4da100fca9ee22cc91689b931f0ed333e81f913c