cts: fix running AnomalyTestCase#testPerfetto multiple times b2b
This CL ensures that running the #testPerfetto test back to back will
not fail because of hitting a guardrail in traced which prevents configs
which don't specify a unique session name from tracing too close
together.
To do this, we need to stop using the explicitly hardcoded bytestring
and instead create the proto bytes programatically so we can introduce
the randomness. This requires adding a dependency on Perfetto's trace
config which is fine as it is already used by the CrystalBall framework
so is well used in Android infra.
(cherry-pick of ag/11913566 needed because this is failing on rvc-dev)
Bug: 157971967
Change-Id: Ic9d94dc527265e51fa523ccfe44cfc1632d51b0c
Merged-In: Ic9d94dc527265e51fa523ccfe44cfc1632d51b0c
2 files changed
