Create a simpler post-clone exp by removing Jasmine as a Git submodule.

It is the only git submodule, that provides no extra benefit as one.

Issue Ref: https://issues.apache.org/jira/browse/RIPPLE-13

Note: Jasmine v1.3.1 was re-added directly into the repo.

!! Important !!

You will probably run into issues when the submodule still
exists in thirdparty/jasmine when rebasing or merging branches.

It feels roundabout, but you clean things up with:

    git rm -rf thirdparty/jasmine
    git reset HEAD thirdparty/jasmine
    git checkout -- thirdparty/jasmine

There are probably other ways, but this ends up with that as an empty
folder, and then this commit will apply cleanly.
Remove support for Git submodules because they are not being used.

This removes use of submodules in the project in general, which
will remove an extra step from 'configure', and ultimately create
a simpler and more straightforward post-clone step (i.e. just npm).