test(debugger): detect bracketed byteLength at runtime (#8172)

The template integration test compared its output against a hardcoded
`util.inspect` string and version-gated the bracketed `[byteLength]` form
on `>=24.11.1`. The same change was later backported to Node.js v22.22.1,
which broke `node-active` on master once GitHub Actions started serving
v22.22.x to that job (PR CI happened to land on v22.22.0 and stayed
green).

Probe the current `util.inspect` output for `[byteLength]` instead, so
the assertion tracks Node's actual behavior on whatever patch the runner
picks up. This avoids having to enumerate every release line that
backports the change.

Refs: nodejs/node#60131
Refs: #8140

Author: BridgeAR

integration-tests/debugger/template.spec.js

@@ -1,11 +1,12 @@
 'use strict'
 
 const assert = require('node:assert/strict')
-const semver = require('semver')
+const { inspect } = require('node:util')
 const { NODE_MAJOR } = require('../../version')
 const { setup } = require('./utils')
 
-const NODE_24_11_1_OR_LATER = semver.gte(process.version, '24.11.1')
+// Backported across LTS lines, so detect at runtime instead of version-gating.
+const HAS_BRACKETED_BYTELENGTH = inspect(new ArrayBuffer(0)).includes('[byteLength]')
 
 describe('Dynamic Instrumentation', function () {
   describe('template evaluation', function () {
@@ -100,7 +101,7 @@ describe('Dynamic Instrumentation', function () {
           messages.shift(),
           'ArrayBuffer { ' +
             '[Uint8Contents]: <00 00 00 ... 7 more bytes>, ' +
-            (NODE_24_11_1_OR_LATER ? '[byteLength]' : 'byteLength') +
+            (HAS_BRACKETED_BYTELENGTH ? '[byteLength]' : 'byteLength') +
               ": 10, '0': 0, '1': 1, '2': 2, '3': 3, '4': 4, '5': 5, '6': 6, '7': 7, '8': 8, '9': 9 " +
           '}'
         )