AOSP and Google list are split it misleading ways

[note] not sure if you consider this a bug, but I wasn't quite sure which category to pick

some com.google.android.* packages are actually part of AOSP (and in fact open source, at least upstream), and the reason they are in a com.google package is (to my understanding) that this signifies that Google "owns" them, and an OEM is not supposed to change them in any way (unlike most AOSP code, where changes are generally allowed as long as the CTS still passes). These packages should therefore be in the AOSP list, or possibly in a separate list, but it's very much misleading for them to be in the Google list along actual spyware.

I don't have a list of which are which, but it should be reasonably trivial to check for each package in the Google list if the sources for it are available in AOSP (since such sources are going to contain the package ID at minimum inside the manifest)

The issue is about the package lists in the universal-android-debloater tool. First, examine the code that defines the AOSP and Google package lists, likely in a data or configuration directory. For each package in the Google list, check if its source is available in AOSP by looking for the package ID in AOSP manifests. The goal is to move packages that are open-source from the Google list to the AOSP list or a separate list.

Written by the indexing model from the issue text.