Revoking camera access in browser mutes remote track but doesn't mute local track

[davideberlein]

Describe the bug

Steps to reproduce

1. start a call
2. publish a MediaStreamTrack using room.localParticipant.publishTrack(videoTrack,...)
3. revoke camera access permission (in chrome)

Expected behavior

• The LocalTrackPublication is muted and the localTrackMuted event is triggered
• The RemoteTrackPublication is muted for anyone subscribed to the published camera and the trackMuted event is triggered.

Actual behavior

• The LocalTrackPublication is not muted and no localTrackMuted event is triggered (however the LocalTrackPublication.isUpstreamPaused is set to true and the LocalTrack.upstreamPaused event is trigged)
• The RemoteTrackPublication is muted for anyone subscribed to the published camera and the trackMuted event is triggered.

System Info

OS: Mac OSX 12.5.1 (21G83)
Browser: Chrome Version 106.0.5249.61 (Official Build) (arm64)
livekit-js: 1.5.0

Severity

serious, but I can work around it

Additional Information

It looks like LocalParticipant.onTrackUpstreamPaused handles UpstreamPaused the same way as Muted which is why the state is correctly propagated to the remote participants but not the local participant.