Remove listener

[battk]

Currently jasmine-npm does not remove the exit listener it adds when it executes. This pull moves the exit listener code completely within the completion reporter so that the listener can be added and removed whenever jasmine is started and done. This is basically pull #125 , except that the jasmine interface remains as intact as possible. The only interface change is that the completion reporter now uses jasmineStarted to add the exit listener. The jasmineStarted method can no longer be overwritten without losing the exit check logic. You can close issue #134 after merging. The fix should allow jasmine to be used with things like gulp watch without errors about max listeners.

Unfortunatly I also had to make failing tests pass on Windows since file logic relied on path separators only being / when windows also allows \. The fix will probably make it so that on windows, files aren't required twice. I don't actually think requiring a file twice does any harm, especially with how it is used here.

Unrelated, but I found it ironic that the tests were smart enough to remove the exit listener while the actual code it was testing was not.

[slackersoft]

Looks good. The tests knew they didn't want to actually mess with the outer on exit based on the inner Jasmine being run, and that there might be multiple specs running an entire Jasmine inside Jasmine's suite, so they would need to be removing the handler. Jasmine still really expects to be booted once, have the specs loaded, execute specs, then exit, so wasn't expecting the case where things are run multiple times.