DbView: Recipes with multiple upstream sources

There are some upstream recipes with sources that are unused downstream in Oniro, that would need to be spotted and possibly forked in order to remove any unused sources, that otherwise would end up in Fossology, making the Audit Team wasting time and leading to possible false positives in the IP check.

The main issue currently is just Zephyr and FreeRTOS, since they are the only projects that have single recipes that fetch sources from multiple repos, mainly for hardware support (actually there are some other recipes with multiple upstream sources here and there, but for different reasons).

There should be a database view to enable the dev team to quickly check which recipes have multiple upstream sources and spot potentially unused sources, in order to remove them.