Bugfix / Correct stopping async cell execution

[truongle1501]

Regarding document:

jupyter_client/docs/messaging.rst

Lines 1634 to 1639 in eb96748

	content = {
	# When the kernel starts to handle a message, it will enter the 'busy'
	# state and when it finishes, it will enter the 'idle' state.
	# The kernel will publish state 'starting' exactly once at process startup.
	execution_state : ('busy', 'idle', 'starting')
	}

Context:
The async cell execution stopped too early because it hit the below condition while the cell is being executed. This also means there was a moment when iopub message satisfied both msg["parent_header"].get("msg_id") == msg_id and execution_state='idle'

jupyter_client/jupyter_client/client.py

Lines 560 to 572 in eb96748

	msg = await ensure_async(self.iopub_channel.get_msg(timeout=0))
	if msg["parent_header"].get("msg_id") != msg_id:
	# not from my request
	continue
	output_hook(msg)
	# stop on idle
	if (
	msg["header"]["msg_type"] == "status"
	and msg["content"]["execution_state"] == "idle"
	):
	break

This PR aims to set a flag to allow stopping the cell execution only when it saw 'busy' state, which forces the stop condition to run after cell execution starts.

[minrk]

Thanks! I see that this fixes a status message from a previous cell.

Rather than waiting for busy and then idle, which would have a similar issue, just a bit farther back in time, I think the fix might be to add a check for and msg["parent_header"].get("msg_id") == msg_id to make sure we are stopping on the idle message from this request, rather than any idle message.

[rgbkrk]

Care to rebase this one to get the CI kicked off again fresh?