Differentiate between sub-directory used by sdks and non-sdk components

We have a sub-directory named "shared". Theoretically, a sdk can be
named "shared", in which case we will have another directory
"shared@random". Our logic breaks down in such situations.

In this CL, we isolate logic that scans sub-directories under sdk
package directory and instead of just returning a list, we now create a
class where the different kinds of sub-directories are grouped together.
This allows us to avoid collision between sub-directories created for
sdks and sub-directories created for non-sdk usage.

By putting all our expectations regarding sub-directories in one place,
it makes it easier to add new special sub-directories in future.

Bug: 235321528
Test: atest SdkSandboxStorageManagerUnitTest
Change-Id: Ia81c08e657aa6e0fc66daaa974e776670d06157a
2 files changed
tree: bea28b27e500abb4051d254453e04104ae44a9de
  1. adservices/
  2. apex/
  3. sdksandbox/
  4. groups
  5. OWNERS
  6. PREUPLOAD.cfg
  7. project.config