Allow argument matchers to enhance failure messages

[searls]

I was a little disappointed by this:

eatBiscuit(44)

td.verify(eatBiscuit(td.matchers.isA(Date)))

Error: Unsatisfied verification on test double.

  Wanted:
    - called with `({})`.

  But was actually called:
    - called with `(44)`.

It really seems like the isA matcher should have and use a hook to report something such that we'd see:

  Wanted:
    - called with `([something of type 'Date'])`.

[searls]

(The same goes for all the built-in matchers; the real work here is the hook to modify the argument description)

[samjonester]

This looks like it's already completed, unless there is more you'd like to include with this ticket:

https://github.com/testdouble/testdouble.js/blob/master/src/stringify/anything.coffee#L13
https://github.com/testdouble/testdouble.js/blob/master/src/matchers/index.coffee#L21

[searls]

Do we have a test for something like I pointed out at the top?

[samjonester]

is https://github.com/testdouble/testdouble.js/blob/master/test/src/verify-test.coffee#L97 sufficient?

[searls]

This was indeed fixed when we changed the matchers format to have a name property.