Messages are built, expecting arrays.

This will cut down on API overhead and allow for the matchers to expect based upon arrays, Signal test recorders and Signals themselves
Simplifying and formalising the syntax for building expected: expressions
Non-Signal actual expectation tests
All tests for complete() passing with new messages
errorTests passing
finishTests()
matchValueTests passing
sendErrorTests passing
sendValuesWIthCount passing
Negation for sendValues and sendEvents
sendValues now passing tests
Rendering of expected values/object. All tests now passing
Tests for adding Signal test recorders
matchValues has decent messages as well as test recorder tests
matchValues  takes recorders