Unescape relative path before accessing file provider

The relative path was URL-encoded, which caused file lookups to fail for paths containing spaces or other special characters. Unescaping the path resolves the issue.

Author: jacob-l

src/Components/WebView/WebView/src/StaticContentProvider.cs

@@ -27,6 +27,8 @@ public bool TryGetResponseContent(string requestUri, bool allowFallbackOnHostPag
         {
             var relativePath = _appBaseUri.MakeRelativeUri(fileUri).ToString();
 
+            relativePath = Uri.UnescapeDataString(relativePath);
+
             // Content in the file provider takes first priority
             // Next we may fall back on supplying the host page to support deep linking
             // If there's no match, fall back on serving embedded framework content