'Library' list

[okennedy]

What pain point is this feature intended to address? Please describe.
#18, once fully implemented, will spam the Artifacts list with Python libraries and functions.

Describe the solution you'd like
Subdivide the artifacts list into multiple categories. For now, this can be limited to splitting Libraries off from the rest, and maybe de-emphasizing it (e.g., putting it at the bottom of the list).

If we do this, we could also use the 'fields' positions to provide links to documentation. Some thoughts:

• We could pull out the module's docstring and function list
• We could see if we could dig up enough metadata to link to the project's main docs page.
• We could add documentation on standard Vizier components (e.g., Spark Javadocs)