Jupyter Kernel: Launch the debugger with the current triple in REPL mode

Yeah, I agree that's not very robust. Either of Jim's solutions sound cleaner and more robust.

One thing to note is that this problem might eventually go away on its own if I get around to switching the jupyter kernel to use SwiftREPL.cpp as discussed in this thread. All the initialization code in the jupyter kernel will go away and the kernel will instead call into the SwiftREPL.cpp initialization code that already does the right thing with the triple. I don't have any specific plans about when to do this, so it might be a while though.