Fluent tests are not run in CI

### Description

Looking at CI logs:

```
=== COMMAND LINE ===
"D:\a\_work\1\s\.dotnet\dotnet.exe" test D:\a\_work\1\s\artifacts\bin\PresentationFramework.Fluent.Tests\x64\Debug\net10.0-windows\PresentationFramework.Fluent.Tests.dll --logger:"console;verbosity=normal" --logger:"trx;LogFileName=PresentationFramework.Fluent.Tests_net10.0-windows_x64.trx" --logger:"html;LogFileName=PresentationFramework.Fluent.Tests_net10.0-windows_x64.html" "--ResultsDirectory:D:\a\_work\1\s\artifacts\TestResults\Debug" "--Framework:.NETCoreApp,Version=v10.0" --blame --blame-hang-dump-type full --blame-hang-timeout 10min --blame-crash-dump-type full --collect:"XPlat Code Coverage" --test-adapter-path "D:\a\_work\1\s\.packages\coverlet.collector\6.0.0/build/netstandard1.0" --settings "D:\a\_work\1\s\/eng/CodeCoverage.runsettings"
VSTest version 17.15.0-preview-25302-104 (x64)

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
Blame: Attaching crash dump utility to process testhost (4732).
[xUnit.net 00:00:00.00] xUnit.net VSTest Adapter v2.8.1+ce9211e970 (64-bit .NET 10.0.0-preview.6.25315.102)
No test is available in D:\a\_work\1\s\artifacts\bin\PresentationFramework.Fluent.Tests\x64\Debug\net10.0-windows\PresentationFramework.Fluent.Tests.dll. Make sure that test discoverer & executors are registered and platform & framework version settings are appropriate and try again.
Data collector 'Blame' message: All tests finished running, Sequence file will not be generated.

Results File: D:\a\_work\1\s\artifacts\TestResults\Debug\PresentationFramework.Fluent.Tests_net10.0-windows_x64.trx
Html test results file : D:\a\_work\1\s\artifacts\TestResults\Debug\PresentationFramework.Fluent.Tests_net10.0-windows_x64.html

Attachments:
D:\a\_work\1\s\artifacts\TestResults\Debug\70a03e42-f8c2-4e9f-ab3a-9a2394ea79fd\coverage.opencover.xml

```

### Reproduction Steps

See CI logs

### Expected behavior

Tests are run

### Actual behavior

No tests run

### Regression?

I don't know.

### Known Workarounds

_No response_

### Impact

_No response_

### Configuration

_No response_

### Other information

_No response_