[compiler-rt] [asan][win] Fix CreateThread leak (PR #126738)

[via llvm-commits]

================
@@ -143,9 +143,11 @@ static thread_return_t THREAD_CALLING_CONV asan_thread_start(void *arg) {
 
   ThreadStartParams params;
   t->GetStartData(params);
+  // The ExitThread will end the current thread, causing destroy to be unable to
+  // be called.
+  t->Destroy();
----------------
GkvJwa wrote:

> I think `t` is escaped above, so this isn't correct, it needs to happen after the thread runs.
> 
> If the user thread routine calls [ExitThread](https://learn.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-exitthread) manually rather than returning, then the proper fix for ASan is probably to intercept ExitThread and do the deallocation there.
> 
> Also, it sounds like small memory leaks are expected when calling `ExitThread`, so maybe we shouldn't worry about this:
> 
> > A thread in an executable that is linked to the static C run-time library (CRT) should use _beginthread and _endthread for thread management rather than CreateThread and ExitThread. Failure to do so results in small memory leaks when the thread calls ExitThread.

Yes, But different from CreateThread in static libraries in handling tlsdata issues
The memory allocated through ```Virtualalloc``` itself is not released.(56 bytes are leaked each time)
As a result, my unittest quickly omm

The following demo can be reproduced
```


#include <iostream>
#include <thread>

void test(int i)
{
	std::cout << i << std::endl;
}

int main()
{
	for (int i = 0; i < 10000; i++)
	{
		std::thread t(test, i);
		t.detach();
	}

	char a;
	std::cin >> a;
}

```

I'll try to hook `ExitThread` so that `t` can be released normally.

https://github.com/llvm/llvm-project/pull/126738