Debugger relies on case-insensitive paths

This odd behavior was first noticed in a test:

https://github.com/PowerShell/PowerShellEditorServices/blob/bfe334df7e4bdd4b92c5c0319655e40444e185ff/test/PowerShellEditorServices.Test/Debugging/DebugServiceTests.cs#L140-L141

It turns out that the URIs and paths we're receiving "over the wire" (in the raw LSP requests themselves) are mostly cased correctly, with the exception of driver letters being lower case. Because of this, when https://github.com/PowerShell/PowerShell/issues/20057 was temporarily fixed by making PowerShell's debugger's _pendingBreakpoints collection case-sensitive, it broke the extension's debugger https://github.com/PowerShell/vscode-powershell/issues/4668.

We need to figure out why those drive letters are coming over lower-case, as the rest of the Windows ecosystem doesn't expect drive letters to be lowercase. Worst case scenario is that we fix the casing as we handle the request, but I'd like to see where the issue originates (thinking perhaps in the LSP client library...) and try to fix it there. Though technically c:/ is valid, and it's mostly PowerShell that's caring about it not being C:/.

Beginne mit test/PowerShellEditorServices.Test/Debugging/DebugServiceTests.cs ungefähr in den Zeilen 140–141 und reproduziere das Verhalten bei der Groß-/Kleinschreibung. Verfolge, wie rohe LSP-Anfragen und Pfade mit Laufwerksbuchstaben verarbeitet werden, einschließlich der referenzierten LSP-Clientbibliothek. Als erledigt gilt die Aufgabe, wenn die Ursache der kleingeschriebenen Laufwerksbuchstaben identifiziert ist und das Verhalten des Debuggers durch einen Regressionstest oder eine geeignete Korrektur abgedeckt wird.