vgsp-sema: m157 defer busy-refused GR captures instead of soft-releasing them (R1)

r157 streams2: kernels 2 and 3 were captured while kernel 1's forward was
INFLIGHT, refused by svc_gr_request, and their releases were fabricated in
software 36 us later (the F2.3 fail-open path) - the client read all zeros.
Now a busy refusal (hold active / INFLIGHT / paused, bridge disabled) sets
svc_gr_busy_defer and the entry loop holds the entry under the m150 one-shot
window instead of consuming it, so the pump re-captures and forwards it for
real once the in-flight launch completes. With the bridge enabled the old
behaviour is kept (the bridge job owns the release).

0 files changed, 0 insertions, 0 deletions