add chained expectation descriptions to the default descriptions of custom matchers with fluent interfaces

this fixes #532
In my opinion, it should be configurable per matcher in case someone is using 3rd party matchers mixed with their own, they might not have control over which ones need the chained description etc. We could still look to making this the default in 4.x.