Remove multiple restart feature

[klaussner]

Removes the logic that restarts a crashing Meteor server twice if there is a runtime error.
Fixes meteor/meteor-feature-requests#335.

[klaussner]

Should the beforeRun option be removed from AppRunner? It's only used here.

[klaussner]

This change uncovered a bug in the launchOneMongoAndWaitForReadyForInitiate function, which waits until the database is ready by checking MongoDB's stdout for certain status messages. Under the conditions in the mongo with multiple --port numbers test, this function returns too early, leading to the MongoError: not master and slaveOk=false error shown in Test Group 7.

You can reproduce this with a Meteor app that accesses the database immediately after it started:

import { Meteor } from "meteor/meteor";
import { Mongo } from "meteor/mongo";

const Collection = new Mongo.Collection("collection");

Meteor.startup(() => {
  Collection.findOne();
});

First, run the app with meteor, then stop it and run it again with a different port: meteor --port 4321.

[klaussner]

The failing test in Test Group 8 (mongo with multiple --port numbers) will pass when 2b21a90 is merged into devel.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.