publish: raise dotnet publish verbosity to normal

The default 'minimal' MSBuild verbosity hides the restore, ILC, and
native link steps, which made failures like the Windows arm64 "platform
linker not found" error hard to diagnose from the pipeline logs alone.

Pass -v:normal to dotnet publish in each platform's publish script
(Windows, macOS, Linux, and the .NET tool) so the full toolchain
discovery and link output is captured in CI.

Assisted-by: Claude Opus 4.8
Signed-off-by: Matthew John Cheetham <mjcheetham@outlook.com>

Author: mjcheetham

build/dntool/publish.sh

@@ -86,6 +86,7 @@ verbose "output dir:    $OUTDIR"
 # No runtime identifier is specified, so the output is portable (tools/<tfm>/any).
 info "Publishing .NET tool application..."
 dotnet publish "$GCM_SRC" \
+    -v:normal \
     --configuration="$CONFIGURATION" \
     --framework net10.0 \
     --output "$OUTDIR" \

build/linux/publish.sh

@@ -112,6 +112,7 @@ fi
 info "Publishing application..."
 # shellcheck disable=SC2086 # AOT_ARGS is intentionally word-split (0 or 2 args).
 dotnet publish "$GCM_SRC" \
+    -v:normal \
     --configuration="$CONFIGURATION" \
     --runtime="$RUNTIME" \
     --output "$OUTDIR" \

build/macos/publish.sh

@@ -112,6 +112,7 @@ fi
 info "Publishing application..."
 # shellcheck disable=SC2086 # AOT_ARGS is intentionally word-split (0 or 2 args).
 dotnet publish "$GCM_SRC" \
+    -v:normal \
     --configuration="$CONFIGURATION" \
     --runtime="$RUNTIME" \
     --output "$OUTDIR" \

build/windows/publish.ps1

@@ -77,6 +77,7 @@ if (-not $Aot) {
 # Publish the application to the resolved output directory.
 Write-Information "Publishing application..."
 dotnet publish "$GcmSrc" `
+    -v:normal `
     --configuration $Configuration `
     --runtime $Runtime `
     --output $OutDir `