Add common known sources to skeleton files

[samueldr]

Once #6 done.

---

Some OEMs, or open source ROMs have trivially "guessable" structures.

We could, thus, suggest an src for those.

---

LineageOS

For LineageOS, we have to to follow the dependencies:

• https://github.com/LineageOS/android_device_xiaomi_lavender/blob/fce97f611f0ead461944dd45bc02269517d120f4/lineage.dependencies
• https://github.com/LineageOS/android_device_xiaomi_sdm660-common/blob/26f489134a24e06ae6949b768f1b3433f669e545/lineage.dependencies
• https://github.com/LineageOS/android_kernel_xiaomi_sdm660

Until we find android_kernel* in the sources.

Then I guess at that point we can, while syncing up the branch names, simply add the tip of that kernel source tree.

What do I mean by syncing?

At the current moment the lavender tree only has a linage-17.1 branch, while the xiaomi-sdm660-common repo has a linage-18.0 branch. Just in case things change between versions, we have to keep them synced. Furthermore the kernel might not build for the device in a "future" branch.

---

OEMs

When implementing the LineageOS check, implement in a way where it should be trivial to implement things like:

Xiaomi

Guess the branch on this repo:

• https://github.com/MiCode/Xiaomi_Kernel_OpenSource

By mapping ${codename}-${androidVersionToLetter}-oss branch names.

Oneplus

By mapping the CPU identifier

• https://github.com/OnePlusOSS?q=android_kernel_oneplus&type=&language=

---

Other suggestions

Android Linux Stable

https://github.com/android-linux-stable/

Uh, there's fewer kernels than I anticipated, might not be worth the time to automate this suggestion.