Set thread names for game threads

[p0358]

Adds nice thread names that can be visible in crash dumps, non-attachable debuggers and generally in all places where old method of throwing exceptions to attached debugger on game start wouldn't work:

Can't believe it wasn't already there lol, makes debugging pain without.

Also the method to convert charsets is bad, but that's not my fault, seems Northstar doesn't have any util func for that apparently either, and this "method" was used in some other places in the codebase where it didn't belong. As thread names are generally static it should be fine in this place, but still.

Tested to work as you can see on the screenshot.

[GeckoEidechse]

Uh, where can I see the thread names? ^^"

[p0358]

Many tools, like x64dbg, Very Sleepy debugger, probably in various "process explorer" kind of programs too.

Also worth noting for future reference from RoyalBlue:

if you want names for miles threads as well you need to hook a func there as well because miles only names threads when a debugger is present on thread start
its mileswin64 + 0x3EBD0 a1 is thread handle a2 is the name

https://discord.com/channels/920776187884732556/950322078945538058/1206634307976699905

tested some more and Bink IO is set with just your change already so only the miles hook needs to be done

The above and possibly bink could also be added, but unfortunately for now I cannot be arsed to do that. They might be done in a separate PR though, so I leave that for future reference here. This PR alone makes the situation much nicer already by naming game threads...

[p0358]

Oh also one more thing, this doesn't set the name of MainThread as the hook is done too late. The thread that does the hooking is 99% the main thread, but that should be tested and then when the hook is performed it should set the name of its own thread to "MainThread" then.

[r3muxd]

the real fix for this is to use tier0 to make threads so your TLS gets set up correctly
https://www.unknowncheats.me/forum/counterstrike-global-offensive/335391-fixing-tls-multithreaded-engine-calls.html
for more info as to why this is important read here
particularly you will get weird problems with CMaterialSystem as it uses a CTHREADLOCALPTR for the render context

[GeckoEidechse]

I was told the comment above is not really relevant to the PR...