[wasm][debugger] Fix step behavior

[thaystg]

The case that we would get a different behavior is when we have more than one command being executed in the same line:
var d = TimeSpan.TryParseExact(y, @"ss\.fff", null, out var ts) && x.Contains('S');
When we step over we stop in the same line again, then we need to step over again to go to next line.

• Creating test to test Blazor WASM "step over" doesn't work properly for referenced assemblies #49142
• Fix behavior of step to be the same of what we see when debugging using debugger-libs+mono or coreclr.
• Creating test to close Watch window does not execute ToString() on objects #49143
• Creating test to close Blazor WASM doesn't correctly step through code when debugging #49141
• Creating test to close Blazor WASM debugger faults when stepping through code #49218.
• Fix error message of evaluate calling methods.

NOTE: If we want to backport it to preview7 we also need to backport #55869, otherwise it will break step after hotreload for wasm.

[ghost]

Tagging subscribers to this area: @thaystg
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Creating test to close #49143.

Author:	thaystg
Assignees:	-
Labels:	area-Debugger-mono
Milestone:	-