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

this fixes #532
Yes this could be done - but then this variable is created every time the matcher is used, regardless of if the chained methods are used or not.  Not sure if there are performance overhead concerns with this.  What do you think?