Error wrapping

Trying to answer my own question from #17.

* Wrap an error with a user-visible error message.  
* Add the stack from `runtime.Stack()` at the time the error was created, not [when it's reported](https://github.com/technoweenie/grohl/blob/2bcb53d3f65b2ecb54612869abec02823316c77a/errors.go#L41).  I find this gives more accurate stack traces.
* For web applications, track the HTTP status code to return.
* Errors can return `false` for Reportable().  This way errors can be used for user-visible error messages without being sent to the error reporter.
* Errors can have their own grohl context.

I didn't go with the `errgo` package because it doesn't seem to track the stack trace.  Stack traces are really useful for our high level app code.

Also, this `*grohl.Error` type is not required by grohl at all.  Pass in your own errors, and implement the interfaces that make sense to your use case.
Easy peasy, lemon squeezy: dfd30734832b5bf6462628f03d6c7a4e73a2e9d8.

Grohl doesn't require 1.3 yet, but users can just pick an older rev.  I'm not too concerned about it.