Expose additional jasmine functionality and resolve conflicts in cljs/js equality and truthiness

Here we have support for basic spies (no mocked returns or pass throughs) and the mock clock exposed through cljs macros.  Additionally, the behavior of the `:to-equal` `:to-be-truthy` and `:to-be-falsy` matchers have been changed so that they use the cljs notion of equality and truthiness instead of javascript.  New matchers `:to-be-equal-js` `:to-be-truthy-js` and `:to-be-falsy-js` have been added for cases where the javascript semantics are needed, but the default should be that of cljs.

Also, it's not part of this pull request but there is an implicit dependency on angular being installed into the a `lib` directory as a result of the two angular-specific test cases.  I have removed these test cases in my fork and I would suggest that they either be removed or moved to a separate test suite so that the main test suite can be run without any additional external dependencies (and it just seems weird for angular to be involved since otherwise this is such a general purpose library).

Thanks for starting this project I really like the method name / keyword matching approach you took - very lightweight and easy way to expose most of the built-in matchers.  I'm really happy with how the test cases read when using this library.

Cheers,
Brent Shields