Don't update the compiler filter when using a runtime image.
Before this change, the runtime reports the compiler filter being
"speed-profile" when using a runtime image. This was originally for
reporting the app startup metric under a unique pair of dimension
values (speed-profile, vdex).
However, it turns out that the code that reports the app startup metric
doesn't get the compiler filter from the runtime. Besides, the compiler
filter change can have surprising side-effects. For example, when an app
gets its own optimization status from the Java API
`ApplicationRuntime.getBaseApkOptimizationInfo()`, it may find itself
being in (speed-profile, install) even though its baseline profile is
not used during app install.
Bug: 260557058
Change-Id: I46eb5015f2a382f5363b2bfab15be8c6a86a2f73
Test: Presubmit
4 files changed