add a DB connection module
make jshint work with gently
respond with dummy data from the DB connection
add db interface layer

DB can not be actually used yet
add models/schemas
add population for restaurant and tag names

I don't like testing the connection.js class like that, but I don't
know what I should be doing differently either.
remove commented code
require models

add index.js to require everything in the models folder automatically
add mongo connection
update tests and filters for new data model

i.e. location-> restaurant.name and tags[0]->tags[0].name
update html for model changes
move json data files to /api/ path

this way the files can be used as mocks if the node server is not running
give the API a higher precedence in express
fix jshint warnings
fix mocha tests

the require('./models') had to be mocked out
get rid of Mockery

it wasn't really needed and it broke when instrumentation was used