[Fix] Update Cell execution result and align client and server state

[shibbas]

Checklist

• I have read the Contributor Guide
• I have updated the changelogs/current_changelog.md file with some information about the change that I am making the appropriate file.
• I have validated or unit-tested the changes that I have made.
• I have run through the TEST_PLAN.md to ensure that my change does not break anything else.

Context

Related Issue - #5549

This PR addresses a few things:

• BREAKING: Uses the jupyter messaging protocol defaults for execute_request.stop_on_error.
• BREAKING: Removes the EXECUTE_CANCEL_ALL and instead uses the kernel returned state in execute_reply status to determine whether to cancel a cell or not.
• Adds the execute_reply status to the transient metadata via a new action that can be used by applications to determine the success / failure of the cell or whether the cell was aborted.

Proposal

It looks like client and kernel states on the cell execution get out of alignment around cell errors. Jupyter defaults stop_on_error for execute_request to true which stops execution on the server for the queued up cells. However, the default in nteract/messaging is set to false, so even though on error the client cells are no longer shown as executing, the execution is till happening on the kernel causing the client and kernel to get out of sync.

Before

Due to the error in cell 3, execution on cells 4 and 5 is stopped, but the execution is still happening on the kernel. So when cell 5 is executed, the printed value is something that was never technically executed by the client. (Expected: 1, got 2)

After

Server sends "aborted" for cells 4, 5 which cancels the cell execution and re-running the cell 5 shows the expected output keeping client and kernel in sync.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nteract/site/Hp8zdfYHJGovWJX56xSjmprDdex2
✅ Preview: https://site-git-fork-shibbas-cellexecutionreplaystatus-nteract.vercel.app

[shibbas]

Putting this back into draft to think through using errors message type vs. execute_reply.status for error.

[captainsafia]

Heads up that automatic releases are now enabled on the repo (see #5568 for more info). To support automated releases, please make sure that the commits in this PR adhere to the conventional commit format (see https://www.conventionalcommits.org/en/v1.0.0/). Once this PR is merged, a release will be triggered for the modified packages based on the commit message.

[MSeal]

@shibbas any input needed to help get the last issue you mentioned putting it back into draft status?