Run jasmine:test goal through jetty, resolves issue #142

This pull request brings the jasmine:bdd and jasmine:test closer together by having them both use jetty to run the specs.  This eliminates the need to copy the sources/specs into the `target` directory and also eliminates the need to have a custom `jasmine-lifecycle`.  As a result, we also no longer need to include `<extensions>true</extension>` in the plugin configuration.

The following still needs to be completed before this pull request is merged in:
 * Rename classes/variables like `CreatesManualRunner` to something more generic like `CreatesRunner`
 * Add some parameter validation before starting the jetty server so we can avoid starting it if we already know our configuration is wrong. An example would be validating that if a `customerRunnerTemplate` is provided then the file actually exists.  Currently, this would start jetty and then you would get a FileNotFoundException in jetty's standard error and then the build would fail with a long stack trace from HtmlUnit complaining that you tried to run javascript on a plain text file.  So, needless to say, it might take awhile for a user to figure out what happened.
 * Currently, all the paths to the source files and spec files use the relative path like `src/main/scripts` in the spec runners but it would make more sense if the used the value of the `srcDirectoryName` and `specDirectoryName` parameters (which default to `src` and `spec`, respectively).

I will work on those items above over the next few days.