Rework command listener for interactive window

[joyceerhl]

We introduced promise chaining in the interactive window to fix a problem in the interactive window where cells executed in rapid succession would get executed out of order:

vscode-jupyter/src/client/datascience/interactive-window/nativeInteractiveWindow.ts

Lines 385 to 393 in 2b3fdb7

	// Chain execution promises so that cells are executed in the right order
	if (this.executionPromise) {
	this.executionPromise = this.executionPromise.then(() =>
	this.createExecutionPromise(code, fileUri, line, isDebug)
	);
	} else {
	this.executionPromise = this.createExecutionPromise(code, fileUri, line, isDebug);
	}
	return this.executionPromise;

This doesn't work very well, because the chained promises do not get correctly cancelled on an interrupt or restart. It also doesn't address problems like #6982. Instead we should use the CellExecutionQueue to queue cells for execution

[amunger]

This is already complete for cells added from a python file, kernelExecution holds a map of ExecutionQueues per document. Code executed from the input box does not go through the same queue since vscode core calls the execution, but that is accounted for in #10671