[wasm][debugger] Fixing memory corruption

[thaystg]

As @pavelsavara detected the code that I wrote was corrupting memory on Module.HEAPU8.buffer, it was reusing the beginning of this heap everytime that was sending debugger commands.
I think we should backport it to rc2.

@lewing can we backport?

Thanks a lot @pavelsavara

[ghost]

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

Issue Details

---

As @pavelsavara detected the code that I wrote was corrupting memory on Module.HEAPU8.buffer, it was reusing the begin of this heap everytime that was sending debugger commands.
I think we should backport it to rc2.

@lewing can we backport?

Thanks a lot @pavelsavara

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

[lewing]

/backport to release/6.0-rc2

[github-actions]

Started backporting to release/6.0-rc2: https://github.com/dotnet/runtime/actions/runs/1258574584

[ghost]

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

Issue Details

---

As @pavelsavara detected the code that I wrote was corrupting memory on Module.HEAPU8.buffer, it was reusing the begin of this heap everytime that was sending debugger commands.
I think we should backport it to rc2.

@lewing can we backport?

Thanks a lot @pavelsavara

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

[radical]

As @pavelsavara detected the code that I wrote was corrupting memory on Module.HEAPU8.buffer, it was reusing the begin of this heap everytime that was sending debugger commands.

What did the failure look like?

[thaystg]

We don't detect any failure, @pavelsavara saw that the code was strange by reading it to refactor.