add ability to set a catch-all route that returns a 404.  simulates that covet post/delete routes still work if the app being tested has a catch-all route
Reimplemented without changes to covet's options

By passing in an application that was wired up to
exhibit the behavior we wanted to watch out for, I 
was able to get the test failure we needed without
making test-only changes to covet or its config options
refactored to nestle the underscore shenanigans
require things at the top for clarity
Merge pull request #4 from testdouble/route-order

add ability to set a catch-all route that returns a 404.  simulates that...