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)

該 issue 是關於 universal-android-debloater 工具中的套件清單。首先，檢查定義 AOSP 和 Google 套件清單的程式碼，很可能在資料或設定目錄中。對於 Google 清單中的每個套件，透過在 AOSP 清單中查找套件 ID 來檢查其原始碼是否在 AOSP 中可用。目標是將開源的套件從 Google 清單移動到 AOSP 清單或單獨的清單中。

由索引模型根據 Issue 內容生成。