[release/6.0-rc2][wasm][debugger] Fix reuse buffer

[thaystg]

Backport of #59773 to release/6.0

When the wasm linear memory has to grow it invalidates existing views into the heap. To avoid this issue make sure to always create a new view into the heap for the debugger command immediately before use.

Customer Impact

Debugging will eventually fail once the runtime allocates enough memory to require growing the Wasm memory buffer.

Testing

Tested manually on Blazor
Tested on debugger-tests

Risk

Low risk, it's reseting the _debugger_heap_bytes always before the usage to avoid using an invalid pointer in the case that Module.HEAPU8.buffer is reallocated.

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

Backport of #59773 to release/6.0

Customer Impact

Debugger is not working from VS.

Testing

Tested manually on Blazor
Tested on debugger-tests

Risk

Low risk, it's reseting the _debugger_heap_bytes always before the usage to avoid using an invalid pointer in the case that Module.HEAPU8.buffer is reallocated.

Author:	thaystg
Assignees:	-
Labels:	arch-wasm, area-Debugger-mono
Milestone:	-

[lewing]

Retargeted to rc2 and approved per email discussion.

[lewing]

/azp run runtime

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[lewing]

cc @Anipik