api: dont put schema below api, just make it the api endpoint

Makes more sense for clients.  Given an API base path (/api/v1/), you
make a request to that endpoint (given that you don't know that
/api/v1/schema/ without some more out of band information).  From there,
the api gives you everything you need via the schema.

Its not clear if we really need /schema/ endpoints for each resource.
Since the api schema dumps all of this at the moment.  Not sure why
you'd want to split it out?
resource: add todo about subresources vs current behavior
resource: more comments on todo