Interactions: Fix various inconsistencies

[ghengeveld]

Issue: #16426

What I did

Fixed how parentId is propagated to nested calls.
Deduped and sorted the call log so it neatly maps on top of the shadow log (used while debugging), fixing weird behavior with waitFor (and potentially other callbacks).

How to test

• Is this testable with Jest or Chromatic screenshots? no
• Does this need a new example in the kitchen sink apps? no
• Does this need an update to the documentation? no

If your answer is yes to any of these, please make sure to include it in your PR.

[nx-cloud]

Nx Cloud Report

CI ran the following commands for commit 161598a. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status	Command
	nx run-many --target=prepare --all --parallel --max-parallel=15

---

Sent with 💌 from NxCloud.

[nx-cloud]

Nx Cloud Report

We didn't find any information for the current pull request with the commit f9f09ef.
You might need to set the 'NX_BRANCH' environment variable in your CI pipeline.

Check the Nx Cloud Github Integration documentation for more information.

---

Sent with 💌 from NxCloud.

[yannbf]

I tested this out and I have two videos explaining some issues I found when interacting:

First, stepping through works great 👍 however clicking directly to the last step fails, as well as when refreshing the browser:

observations-1.mov

[yannbf]

Another observation which is a bit more concerning. When the clicking directly to the last step (fails) and rerunning the interaction + clicking again to the last step, every other story gets affected, even the ones that don't have interactions:

observations-2.mov

[ghengeveld]

What happens is the action does get invoked when clicking the last row, but the assertion happens too soon and it's not retried because waitFor is never retried while debugging. What we should do is allow the user to click 'next' to trigger a retry manually.

[MichaelArestad]

What we should do is allow the user to click 'next' to trigger a retry manually.

I wonder if retrying when there is an error is common enough to justify a retry action/link/button in the error message itself.