* Consistently use app-listings and library-variants internally

This is a helpful step to enable adding endpoints for "applications"
and "libraries", which are nested views of this info.

It's currently confusing that we use "applications" for the flattened
data internally, but use app-listings for that concept in the API.

* Push the listing and variant terminology to API yaml

* Run black