ABI: implement exact remote inspector process controls

[chrisbbreuer]

Parent: #134
Related: #140, #163, #164

Goal

Implement the five shared process-wide JavaScriptCore remote-inspector controls:

• JSRemoteInspectorDisableAutoStart
• JSRemoteInspectorStart
• JSRemoteInspectorSetLogToSystemConsole
• JSRemoteInspectorGetInspectionEnabledByDefault
• JSRemoteInspectorSetInspectionEnabledByDefault

Acceptance

• Preserve independent process-wide auto-start, explicit-start, system-console logging, and inspection-enabled-default state.
• Make all state transitions race-free and idempotent; disabling auto-start must not prevent explicit start.
• Keep the default-enabled getter coherent with concurrent setters.
• Add focused transition/concurrency coverage and compile-link-runtime fixture calls for all five symbols.
• Refresh Home/Bun inventories and public/private classification with zero unclassified symbols.
• Update README and compatibility docs, publish small implementation/docs commits on origin/main, and close only after evidence is live.

[chrisbbreuer]

Implemented and published in two direct main commits:

• e1380f85 — five process-wide atomic remote-inspector controls, idempotent one-way auto-start disable and explicit start, deterministic target default, concurrency coverage, and all fixture calls
• e46767a3 — README and compatibility evidence/count refresh

Verification:

• focused remote-inspector matrix: 3/3 passed, 0 leaked
• Home fixture: 224/224 symbols linked and runtime matrix passed
• Home inventory: 225/431 implemented, 206 pending
• Bun core inventory: 219/421 implemented, 202 pending
• public/private audit: 117 public, 19 extensions, 229 private/support exports
• zero unclassified inventory entries

The benchmark artifact remains 36a617b3: this was an ABI-only process-control slice and does not change measured execution performance.