Adopt Dinah.Core 10.2.5.1 and AudibleApi 11.0.4.1

[rmcrackan]

What

Moves all six sibling package references onto the newly published versions:

Project	Package	From	To
FileManager	Dinah.Core	10.2.4.1	10.2.5.1
DataLayer	Dinah.Core	10.2.4.1	10.2.5.1
DataLayer	Dinah.EntityFrameworkCore	10.2.4.1	10.2.5.1
_Demos/LoadByOS/CrossPlatformClientExe	Dinah.Core	10.2.4.1	10.2.5.1
LibationWinForms	Dinah.Core.WindowsDesktop	10.2.4.1	10.2.5.1
AudibleUtilities	AudibleApi	11.0.3.1	11.0.4.1
LibationFileManager	AudibleApi	11.0.3.1	11.0.4.1

Why

Both upstreams moved their .NET 10 dependency floors to 10.0.11 and published under new versions:
Dinah.Core / Dinah.EntityFrameworkCore / Dinah.Core.WindowsDesktop 10.2.5.1 from
rmcrackan/Dinah.Core#28 and
#30, and AudibleApi 11.0.4.1 from
rmcrackan/AudibleApi#80. This is the last repo in
that chain.

Verification

• dotnet restore Source/Libation.slnx resolves Dinah.Core 10.2.5.1, Dinah.EntityFrameworkCore 10.2.5.1, Dinah.Core.WindowsDesktop 10.2.5.1 and AudibleApi 11.0.4.1, with no new warnings.
• LibationAvalonia, LibationCli and LibationWinForms all build with 0 errors.
• dotnet test from Source/: 1479 total, 0 failed, 23 skipped - unchanged.

Note on NU1903

Restore still reports the SQLitePCLRaw.lib.e_sqlite3 2.1.11 advisory on this branch, and that is
expected. DataLayer references Microsoft.EntityFrameworkCore.Sqlite 10.0.7 directly, and that
reference is what pulls the vulnerable native bundle; picking up Dinah.EntityFrameworkCore's new
EntityFrameworkCore.Relational 10.0.11 floor does not change it. The Sqlite bump that clears the
warning is #1974.

Related

Independent of the two other open PRs, #1974 and
#1975. #1974 also touches
DataLayer/DataLayer.csproj and LibationFileManager/LibationFileManager.csproj, but on different
lines (Microsoft.* versions rather than the Dinah.* / AudibleApi ones), so they merge in either
order.