tree 841d9bdd7a56545cda9da8e02d076eb6d44bb325
parent c468c0ed0cc5d86d9c9c88345c9e7116fb8f213f
author Yurii Zubrytskyi <zyy@google.com> 1707526750 -0800
committer Yurii Zubrytskyi <zyy@google.com> 1707530027 -0800

Reapply "[res] Optimize idmap data initialization in OMS"

The commit got reverted because of a performance regression.
This change is trying to pinpoint it with the steps:

1. Split out the smaller optimizations that are either safe,
   or at least can be easily reverted separately

2. Put the risky optimization that changes the overlayable-
   related JNI calls in the last CL (here)

Original commit message:
    [res] Optimize idmap data initialization in OMS

    - Only load overlayable definitions for the needed apks
      intead of parsing their all resource tables
    # ^^ this is the current CL

    - Don't load any overlayable definitions for checking
      actor policies if no actor policies are defined for the
      device. Almost no one defines any
    # ^^ this part is separated

    - Reduce the number of allocations for the most common
      operations in overlay settings
    # ^^ this part is separated

Bug: 282215580
Test: system boot + perf trace

This reverts commit b63b69c5fe821b1936d389df7dbd99f15247a209.

Change-Id: I20c89d78b8f88e60bb4050a936e0b930f6386ad8