fix(ci): remove --no-build from release.yml test steps

dotnet build RegiLattice.sln does not guarantee all test DLLs are
present — CLI.Tests may be skipped due to build ordering. Removing
--no-build allows each test step to perform an incremental self-build
(fast) before running. Mirrors ci.yml which correctly uses --no-restore
only. This was the root cause of the Test(CLI) 'DLL not found' failure
in the v6.23.0 and v6.22.0 release runs.

Author: RajwanYair

.github/workflows/release.yml

@@ -51,23 +51,23 @@ jobs:
       - name: Test (Core)
         run: >-
           dotnet test tests/RegiLattice.Core.Tests/RegiLattice.Core.Tests.csproj
-          -c Release --no-build --no-restore
+          -c Release --no-restore
           --settings tests/.runsettings
           --blame-hang-timeout 30s
           --logger "console;verbosity=minimal"
 
       - name: Test (CLI)
         run: >-
           dotnet test tests/RegiLattice.CLI.Tests/RegiLattice.CLI.Tests.csproj
-          -c Release --no-build --no-restore
+          -c Release --no-restore
           --settings tests/.runsettings
           --blame-hang-timeout 30s
           --logger "console;verbosity=minimal"
 
       - name: Test (GUI)
         run: >-
           dotnet test tests/RegiLattice.GUI.Tests/RegiLattice.GUI.Tests.csproj
-          -c Release --no-build --no-restore
+          -c Release --no-restore
           --settings tests/.runsettings
           --blame-hang-timeout 30s
           --logger "console;verbosity=minimal"