`<MauiAsset>` is hard to use

Description

I added a <MauiAsset Include="Resources\Assets\*"> in my project and I was unable to easily find how to retrieve it. I used Essentials’ FileSystem.OpenAppPackageFileAsync and I found that it went to different folders:

• Windows => Assets\Resources\Assets*
• Android => Resources\Assets*
• iOS/MacCat => error : The name ‘Resources’ is reserved and cannot be used.

[mattleibow]

@Eilon I think whatever we do is going to affect Blazor. I think we need to get that #791 change in. Just looking at your issues, I see there are a few around this.

We probablu need somehting for Blazor (that can convert to a MauiAsset under the hood with special values), but right now we need something way better than what we have.

[Eilon]

Notes from meeting with @mattleibow :

1. Remove “Assets” special folder from Windows targets in Resizetizer to make it consistent with other platforms
2. Consider updating project template to have MauiAsset glob a. Add glob to template: <MauiAsset Include="Resources/Raw/**" LogicalName="%(RecursiveDir)%(FN)%(EXT)" /> b. Add a sample raw resource “txt” file to “Resources/Raw/asset.txt” --> the content of this file can show the code to read it using Essentials.OpenPackageFileAsync() c. Fix the bug where LogicalName doesn’t work on some platforms
3. Remove “Assets” path combine workaround from BlazorWebViewHandler on Windows: src\BlazorWebView\src\Maui\Windows\WinUIWebViewManager.cs
4. Fix up any samples in the MAUI repo to be more consistent with how we expect MauiAssets to be used