[Detection] Thread inlineParallelCapable through regex pattern path, dedup key, and intelligence graph

[AndresL230]

Follow-up from Wave 3 / PR #126 (#116). The inlineParallelCapable fingerprint flag is wired through the AST detector path (where #116's acceptance criteria are met) and into core-scanner/EndpointRecord, but is not yet threaded into several detection-layer consumers that already handle batchCapable. None is a regression; the default AST path produces the correct "use the n/count parameter" suggestion.

Gaps (each parallels an existing batchCapable site):

• Regex pattern path — src/scanner/patterns/openai-compatible.ts reads reg?.batchCapable with a hint-regex fallback but has no inlineParallelCapable path; src/scanner/local-waste-detector.ts (the regex-only waste detector) has no inline-parallel finding. Net effect today: in RECOST_DISABLE_AST=1 / regex-only files, a DALL·E call in a loop emits no finding (previously a wrong "batch" finding — net-neutral, but the correct n/count suggestion isn't produced via this path).
• Pattern dedup key — src/scanner/patterns/utils.ts dedup key includes batchCapable but not inlineParallelCapable; couple this with the pattern-path fix so distinct matches aren't collapsed.
• Intelligence graph — src/intelligence/types.ts ApiCallNode + src/intelligence/builder.ts coerce batchCapable but drop inlineParallelCapable, so AI-review context can't distinguish the two shapes.

Refs: #116, PR #126.