nextest: retain the integration guard while bounding owner crash tests

Put owner_crash_reentry in its own override of the same spawns-binaries
group. This is equivalent to the union filter for process limits, while
preserving the existing release-workflow assertion for binary(integration).

The first hosted Version drift check on 35498ef68b failed with
"nextest must bound the integration binary". This fixes that guard failure
without changing a test or weakening the group limit.

Verification:
- release-workflows.test.js: 13 hermetic checks passed; 11 wrapper event
  cases x 12 steps; workflow contracts passed.
- check-versions.sh --range-audit-advisory: exit 0, including
  "test result: 10 passed; 0 failed" for dev-test wrapper checks.
- The compiled macOS crash test remains unchanged (1 passed; 0 failed);
  hosted Windows execution on the final candidate still gates the tag.

Refs #6915
Refs CW-7079

.config/nextest.toml

@@ -89,7 +89,11 @@ test-group = 'exec-persistent-service'
 slow-timeout = { period = "120s" }
 
 [[profile.default.overrides]]
-filter = 'binary(integration) | binary(owner_crash_reentry)'
+filter = 'binary(integration)'
+test-group = 'spawns-binaries'
+
+[[profile.default.overrides]]
+filter = 'binary(owner_crash_reentry)'
 test-group = 'spawns-binaries'
 
 # CI (profiles inherit from default): the final summary lists every failure and