pointerlock controls example : fix key listeners

[felixmariotto]

Issue : the pointerlock example, FirstPersonControls and FlyControls checked the keyCode property of the keydown and keyup events, which means it was bound to characters. Some keyboard layouts, like the French one displayed bellow, don't map the WASD keys at the same place, whereas we actually play with the same keys as everybody, only these keys represent different characters.

The present PR solves this by using the event.code propery, which is layout-independant. It will also solve the problem for Russian or Chinese layouts for instance.

[Mugen87]

It's probably best to only change misc_controls_pointerlock in this PR and clean up the code base when it was merged.

Especially after a PR was approved, it's problematic to add more commits (since it invalidates existing reviews).

Code was changed after review.

[felixmariotto]

It's probably best to only change misc_controls_pointerlock in this PR and clean up the code base when it was merged.

@Mugen87 Yes sorry, initially I just thought of fixing this example, but I found a lot more with problems... I'm done checking the examples now, I will do as you said 👍

[felixmariotto]

@Mugen87 I reverted to the state it was at when you reviewed it, and I will make a new PR for the rest of the changes, including the changes in examples/js.
Shall I squash the commits, or is it better to keep them separate ?

[Mugen87]

Shall I squash the commits, or is it better to keep them separate ?

In this PR it seems you have force-pused which is totally fine.

[mrdoob]

Thanks!