Provide a code search subdomain for packaging upstream source and PKGBUILDs

Idea proposal 💡

Checks

NOTE: The below check boxes must be checked before the accompanying idea will be considered.

• I have checked that the idea is not directly tied to a specific project For example: "Show label icons in the package overview web page" must be a feature request in the ArchWeb repository
• I have carefully checked this idea is not already covered by any open or closed ideas.
• I understand that I hold no copyright claims and that this idea can be adapted and used by Arch Linux in any arbitrary shape or form.

Summary

Provide a code search subdomain with a fast UI for searching though packaging upstream sources as well as PKGBUILD sources.

Motivation

Often we face the issue that we need to dig into searching upstream usage of certain code. One example is to find outdated python mock import usage to assess transition and todo lists. Furthermore this can be very helpful for security analysis as well to find certain issues or interesting places when a specific code needs to be diged up. Besides upstream sources, it can also be very helpful to get a UI with strong search capabilities searching through our packaging PKGBUILDs no collect information or find problems.

Specification

We need to scrape all sources during or after package building and transfer it as input to the code search server. We explicitly should not expose the UI on the build server to reduce exposure. A dedicated subdomain should be used exposing the UI to search through both, the packaging sources and the upstream sources. One example for a good subdomain could be sources.archlinux.org or codesearch.archlinux.org. We may want to link to this side somewhere on our main page so users and packagers will actually be aware as well.