Make profiling CTS test non debuggable

When an app is not debuggable, perfetto will make extra checks before
capturing stack samples, heap profiles, or java heap dumps.

By making the CTS test non debuggable we can (manually, for now) check
what's happening with non debuggable apps, which is the most interesting
case.

Test: atest ProfilingFrameworkTests and check the captured traces
Bug: 335688597
Flag: EXEMPT - day-to-day bugfix
Change-Id: I87603eb06b7c68684b955e93bc07d7a2d72f04a8
1 file changed