Include Microsoft.WindowsDesktop.App and host folder in DLL search path

[breyed]

For .NET (Core and 6+), I added paths in CoreClrHost.cpp for Microsoft.WindowsDesktop.App to supplement the existing paths to Microsoft.NETCore.App. This allows FoxPro to use Windows Forms and WPF. If only core is installed (no desktop), the extra path element will be ignored.

I also included the directory of ClrHost.dll to the .NET assembly search path. This allows users to conveniently package all their DLLs (including ClrHost.dll and wwDotNetBridge.dll) in a single folder.

[Copilot]

Pull Request Overview

This PR enhances the .NET Core CLR host to support Windows Desktop applications and improve assembly loading paths. The changes enable FoxPro to use Windows Forms and WPF by adding Microsoft.WindowsDesktop.App to the assembly search path, while also including the host DLL's directory for more convenient deployment.

• Added Microsoft.WindowsDesktop.App framework path to TPA list for Windows Forms/WPF support
• Included the host DLL directory in assembly search paths for easier deployment
• Refactored path building code for better maintainability

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Adding the desktop path without verifying it exists could cause BuildTpaList to process an invalid directory. Consider checking if the desktop path exists before calling BuildTpaList to avoid potential issues when only .NET Core is installed.

Suggested change

	BuildTpaList(desktopPath.c_str(), ".dll", tpaList); // Desktop must come first so that its assemblies take precedence over .NET Core assemblies when the same assembly is present in different forms in both runtimes (e.g. WindowsBase.dll).
	DWORD desktopPathAttr = GetFileAttributesA(desktopPath.c_str());
	if (desktopPathAttr != INVALID_FILE_ATTRIBUTES && (desktopPathAttr & FILE_ATTRIBUTE_DIRECTORY)) {
	BuildTpaList(desktopPath.c_str(), ".dll", tpaList); // Desktop must come first so that its assemblies take precedence over .NET Core assemblies when the same assembly is present in different forms in both runtimes (e.g. WindowsBase.dll).
	}

[Copilot]

Using a fixed-size buffer with GetModuleFileNameA without checking the return value could lead to truncated paths on systems with very long path names. Consider checking the return value and using GetModuleFileNameA's return value to verify the path wasn't truncated.

Suggested change

	char path[MAX_PATH];
	GetModuleFileNameA(hModule, path, MAX_PATH);
	DWORD length = GetModuleFileNameA(hModule, path, MAX_PATH);
	// If the function fails or truncates, return empty string
	if (length == 0 || length == MAX_PATH) {
	return "";
	}

[Copilot]

[nitpick] The method chaining on a single line makes the code harder to read and debug. Consider breaking this into separate append calls or using a more readable string building approach.

Suggested change

	appPaths.append((const char *)curDir).append(FS_SEPARATOR).append("bin");
	appPaths.append((const char *)curDir);
	appPaths.append(FS_SEPARATOR);
	appPaths.append("bin");