Startup scripts (follow up on #241)

1. Added startup scripts to `MCT_DIST/bin` for Windows and Unix-like operating systems. Currently they're very simple, i.e. don't check whether Java is installed, etc.
2. Removed `startup-1.8b4.jar` from the root of the distribution archive (it was present in two folders, root and lib).
3. The startup script refers to `MCT_DIST/lib/startup-1.8b4.jar`. I had to update class path entries in `META-INF/MANIFEST.MF` to reflect this new location of `startup-1.8b4.jar`.

<hr>
1. Wrote or re-wrote unit tests (Y/N): N (Manually tested platform launching on Windows 7 and Cygwin.)
2. Ran entire suite of unit tests successfully (Y/N): Y
3. Verified bug fix with the described replication steps or verified the implementation meets the requirement cited (Y/N): Y
4. Code coverage requirements satisfied (new code=80%, changed code=at least as high as existing) (Y/N): N/A
5. Code review date and attendees: Github pull request
6. Describe potential impact on other areas of the code: No impact. In the worst case MCT won't start at all.
7. Describe any test prerequisites for this fix (e.g., restart the database): N/A
8. For bugs marked "Regression - Yes", describe the cause of the regression: N/A
9. Did you modify any pom.xml file? If yes, did you thoroughly document your changes and reasons? N