Filter replay by Laravel broadcast connection

[luisdalmolin]

Problem

v0.5 records the selected Laravel broadcast connection on each CapturedBroadcast, but every captured connection is still replayed into the current browser session. Events sent through multiple broadcast connections can therefore be delivered more than once to a page that represents only one connection.

Proposed direction

Allow a realtime session to declare the Laravel broadcast connection it represents and replay only matching captures.

Acceptance criteria

• A session can opt into a named Laravel broadcast connection.
• Captures retain the resolved connection for default and explicitly selected broadcasts.
• Replays filter by that connection without losing the unfiltered captured data.
• Events using multiple broadcastConnections() values do not duplicate delivery into one session.
• Default-connection and explicit-connection behavior have Laravel integration coverage.