fix(platform-server): Do not delete global Event

[atscott]

This commit removes a hack that deletes Event from the global context when using domino. Instead, it sets the global event to domino's implementation of Event.

The "Trick to avoid Event patching" links to a state in the repository that is 6(!) years old:

angular/packages/platform-browser/src/dom/events/dom_events.ts

Lines 112 to 132 in 7cf5e95

	private patchEvent() {
	if (!Event || !Event.prototype) {
	return;
	}
	if ((Event.prototype as any)[stopMethodSymbol]) {
	// already patched by zone.js
	return;
	}
	const delegate = (Event.prototype as any)[stopMethodSymbol] =
	Event.prototype.stopImmediatePropagation;
	Event.prototype.stopImmediatePropagation = function() {
	if (this) {
	this[stopSymbol] = true;
	}
	// should call native delegate in case
	// in some enviroment part of the application
	// will not use the patched Event
	delegate && delegate.apply(this, arguments);
	};
	}

. A lot has changed since then. I don't know what the implications might be with this change but @tbondwilkinson and I are encountering issues with events when working with the navigation API that are caused by this bit of hackery.

[atscott]

This PR was merged into the repository by commit f4bd5a3.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}