Add CPU/GPU_LOAD_SPIKE hints for one-off expensive workloads

Currently there is ambiguity between single-frame expensive ops
(eg: shader compilation) and longer-duration expensive ops (eg:
SF client compositon). This load hint aims to resolve this by
explicitly annotating one-time expensive workloads so they can
be given unique boost and hysteresis expectations.

For example, a load_spike aware tracker might want to ignore
the timing that comes from a LOAD_SPIKE-marked frame, as it is
known to not be representative of the overall workload.

Flag: EXEMPT NDK
Test: atest PerformanceHintNativeTestCases
Test: atest PerformanceHintManagerTest
Bug: 367803904
Change-Id: I22458f0d8f0819499f3463aa36e8bb7eb7af15be