github-actions: use inputs.no_pr != true to avoid GHA boolean coercion

Address review feedback on the no_pr guard: `!inputs.no_pr` can be
ambiguous in GitHub Actions expressions because boolean inputs may
arrive as the string 'true'/'false' in some contexts, where the
negation `!` would always evaluate to false (strings are truthy).
Switch to explicit `inputs.no_pr != true` comparison which is robust
across both boolean and string forms.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: kemotaha

.github/workflows/kernel-build-and-test-multiarch.yml

@@ -1202,14 +1202,16 @@ jobs:
     name: Create Pull Request
     runs-on: kernel-build
     needs: [pre-setup, setup, build, boot, test-kselftest, compare-kselftest, test-ltp, compare-ltp]
-    # The (workflow_dispatch || !no_pr) clause lets manual reruns opt out of
-    # PR creation by passing -f no_pr=true. workflow_run events (normal CI)
-    # are unaffected since inputs.no_pr is not set there.
+    # The (workflow_dispatch || no_pr != true) clause lets manual reruns opt
+    # out of PR creation by passing -f no_pr=true. workflow_run events (normal
+    # CI) are unaffected since inputs.no_pr is not set there. The explicit
+    # `!= true` form avoids the boolean/string coercion ambiguity that affects
+    # `!inputs.no_pr` in some GHA expression contexts.
     if: |
       always() &&
       needs.build.result == 'success' &&
       needs.boot.result == 'success' &&
-      (github.event_name != 'workflow_dispatch' || !inputs.no_pr)
+      (github.event_name != 'workflow_dispatch' || inputs.no_pr != true)
 
     steps:
     - name: Check if branch name matches a supported pattern