fix: improve camera access error handling and permission checks

[Sembauke]

onsuspend event fires on media elements (like <video> or <audio>) when the browser intentionally pauses loading more data because it has enough buffered, or the browser chooses to suspend further data fetching temporarily.

I can't test this well because my camera is built-in. I don't think we really have to worry about permissions being revoked during the exam. I suspect/assume that when revoking permissions during the exam will cause them to take effect after re-launching the environment.

The first permission check (when you start up the environment) only checks if the access wasn't granted. Thus giving a "denied" message. But on MacOS the camera permission state will start with "prompt". Although the permission already has been granted in development. If we want to change this behaviour I suspect that we need to reset those permissions when starting a new dev session.

[ShaunSHamilton]

This works well on my end.

Only suggestion is to use the .on<method> assignment pattern, because any event listener needs to be removed on clean up. This gets around needing to do that, because once the track is garbaged, there is nothing for us to clean.