Fix native backends

[ThomasFOG]

I'm looking into getting the native backends up and running again (just getting it to run on Windows without linkage issues).

@sepcnt I don't where you're at, and I assume that you're running into the same issues.

[sepcnt]

It did fix some issues, however, I am afraid that it is not an optimal solution.
Instead of changing the string type, I removed the StringInterop module totally, since we cannot do stackalloc and CoAlloc on other platforms.
You can check my branch https://github.com/sepcnt/MonoGame/tree/desktopvk
It now only left 8 unit tests across multiple platforms and remains full compatibility.

I am now running into some issues with the shader compiler and still waiting for assistance.

[ThomasFOG]

We'll see where this goes! Just wanted to give you the heads up because I needed this to work in the meantime. Looking forward to all the fixes.

[sepcnt]

I made a PR now: #8903

[tomspilman]

Instead of changing the string type, I removed the StringInterop module totally, since we cannot do stackalloc and CoAlloc on other platforms.

I added this specifically just 3 weeks ago. What was the issue?

[sepcnt]

Instead of changing the string type, I removed the StringInterop module totally, since we cannot do stackalloc and CoAlloc on other platforms.

I added this specifically just 3 weeks ago. What was the issue?

It allocates up to 4x memory and may mess up UTF8 conversion.

[tomspilman]

It allocates up to 4x memory

I don't see the concern with the extra memory. We're not a word processor passing 1000s of words of strings. It won't be noticed and is a small memory trade off for less CPU work passing strings at runtime.

may mess up UTF8 conversion.

How could it do that?