fix(test): resolve duplicate -p flag after rebase onto develop

Rebasing onto develop brought in PR #805's conditional
  if (btracePort > 0) { add -p btracePort }
block, which collides with PR #791's unconditional
  "-p", String.valueOf(getBTracePort())
in runBTraceDynamic — producing two -p flags when a test overrides
btracePort.

Keep the unconditional form, since getBTracePort() already honours
both the develop-style btracePort field (ExtensionLifecycleIntegrationTest)
and the PR-style btrace.port system property (ManifestLibsTests), and
drop the now-redundant conditional block.

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

Author: jbachorik

integration-tests/src/test/java/tests/RuntimeTest.java

@@ -1323,10 +1323,6 @@ private Process attach(
     if (unattended) {
       argVals.add("-x");
     }
-    if (btracePort > 0) {
-      argVals.add("-p");
-      argVals.add(String.valueOf(btracePort));
-    }
     argVals.addAll(Arrays.asList(pid, traceFile.getAbsolutePath()));
     if (cmdArgs != null) {
       argVals.addAll(Arrays.asList(cmdArgs));