Set up endpoint logic for "areas" on Home screen

[mattbarker016]

On the home page are common areas on campus. If a user chooses one of these areas, the app should return a list of Routes that will get the user to the area as soon as possible.

These are the current areas with incomplete stops.
(name: "North Campus", stops: "RPCC, Balch Hall, Appel, Helen Newman, Jessup Field"),
(name: "West Campus", stops: "Baker Flagpole, Baker Flagpole (Slopeside)"),
(name: "Central Campus", stops: "Statler Hall, Uris Hall, Goldwin Smith Hall"),
(name: "Collegetown", stops: "Collegetown Crossing, Schwartz Center"),
(name: "Ithaca Commons", stops: "Albany @ Salvation Army, State Street, Lot 32")

We plan to use one central endpoint for route calculation, with the main parameters being start location, end location, arrival time, and departure time. The end location can be coordinates, a Google Place ID, or a keyword corresponding to each of the areas. Shiv will handle parsing this, but we need to setup the logic for handling the area.

We should call the central endpoint with each bus stop in the area (lat-long) plugged into the end location. Note, the other parameters could possibly change if the user wants to change their preferences for getting to the area.

Complete list of OFFICIAL bus stop names in each area.