public.json: Add 'GET /routes' and 'GET /route/{name}' endpoints

The new endpoints are copied from the drop endpoints, changing 'drop'
-> 'route' and 'id' -> 'name'.

Unlike drop name (e.g. 'Dufur Will-Call'), route names aren't
particularly descriptive (e.g. 'A1') and are unlikely to mutate.
Because the names are immutable, we don't need a separate 'id' field,
and we can just treat the route's name as its identifier.
public.json: Add 'route' query parameter to 'GET /drops'

So you can figure out which drops belong to a route.

Internally, we have additional metadata for each association
(e.g. sequence numbers to order drops along each route), but I don't
think folks using the public API will care about that on a per-route
level.  We probably do want sequence, delivery-offset information,
etc. for route-trip <-> drop associations, but we'll get to that
later.
public.json: Add 'drop' query parameter to 'GET /routes'

So you can figure out which routes service a drop.  The mirror of
150053e4 (public.json: Add 'route' query parameter to 'GET /drops',
2014-11-14).