fix: suppress WASM0001 sqlite3_config/db_config varargs warnings on TodoApp.Uno browserwasm

The browserwasm head emits a WASM0001 warning for every fixed-arity
P/Invoke overload SQLitePCLRaw.provider.e_sqlite3 ships to work around
sqlite3_config/sqlite3_db_config being variadic (varargs) native
functions. This sample's actual SQLite usage (in-memory EF Core CRUD
via AppDbContext) never calls those functions directly, so the warning
is diagnostic-only noise from the WebAssembly SDK's build-time
native-interop check.

WASM0001 is a standard MSBuild task warning code (emitted via
TaskLoggingHelper.LogWarning in dotnet/runtime's WasmAppBuilder), so it
honors NoWarn like any other build warning - the same suppression
already documented for Blazor WASM in
docs/in-depth/client/advanced/blazor-wasm.md. Suppress it, scoped to
the browserwasm TFM only, following the existing
GetTargetPlatformIdentifier-conditional pattern used for
SuppressTrimAnalysisWarnings in the same file (see #521/#534).

Also add a short note to the Uno Platform sample docs pointing at the
Blazor WASM page for more detail on the warning and how to suppress it
in a consumer's own project.

Closes #543

Author: ahall

docs/samples/todoapp/unoplatform.md

@@ -18,6 +18,14 @@ If you bump into issues at this point, ensure you can properly develop and run U
 !!! info Tested platforms
     The TodoApp.Uno sample is known to work on Android and Desktop.  We have not tested on other platforms.
 
+!!! info WASM0001 warning on the browserwasm head
+    When building the `browserwasm` head, you may see a `WASM0001` warning about native varargs
+    functions (`sqlite3_config`/`sqlite3_db_config`) in the bundled SQLite provider.  This is
+    harmless diagnostic noise from the WebAssembly SDK's native-interop check - the sample's
+    actual SQLite usage never calls those functions directly - and is already suppressed for
+    this sample's `.csproj`.  See the [Blazor WASM support](../../in-depth/client/advanced/blazor-wasm.md#suppress-the-wasm0001-warning)
+    page for more detail on why this warning occurs and how to suppress it in your own project.
+
 ## Deploy a datasync server to Azure
 
 Before you begin adjusting the application for offline usage, you must [deploy a datasync service](./server.md).  Make a note of the URI of the service before continuing.

samples/todoapp/TodoApp.Uno/TodoApp.Uno/TodoApp.Uno.csproj

@@ -66,6 +66,20 @@
         $([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'maccatalyst'
       ">$(MSBuildWarningsAsMessages);MT7156</MSBuildWarningsAsMessages>
 
+    <!--
+      e_sqlite3 (bundled via SQLitePCLRaw.bundle_e_sqlite3, pinned for #492) exposes variadic
+      (varargs) native functions (sqlite3_config/sqlite3_db_config). The WebAssembly SDK's
+      build-time native-interop check flags every fixed-arity P/Invoke overload SQLitePCLRaw
+      ships to work around this (sqlite3_config_none, sqlite3_config_int, etc.) as WASM0001,
+      even though this sample's actual SQLite usage (in-memory EF Core CRUD via AppDbContext)
+      never calls sqlite3_config/sqlite3_db_config directly. This is diagnostic-only noise -
+      WASM0001 is a standard MSBuild task warning code (emitted via TaskLoggingHelper.LogWarning
+      in dotnet/runtime's WasmAppBuilder), so it honors NoWarn like any other build warning.
+      Same documented, NoWarn-suppressible pattern as
+      docs/in-depth/client/advanced/blazor-wasm.md. See #543.
+    -->
+    <NoWarn Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'browserwasm'">$(NoWarn);WASM0001</NoWarn>
+
   </PropertyGroup>
   <ItemGroup>
     <None Remove="Assets\AddItem.png" />