Feat: More controls for ui.scene

[evnchn]

Motivation

Addresses NiceGUI Wishlist (view), how we are stuck with OrbitControls

Implementation

• Grab all of the controls related to moving the camera
• Add setup_controls and fetch_controls to scene.js
• Add THREE.Clock(); and feed the delta to get FlyControls and FirstPersonControls happy.
• Some controls don't have target. Use this.controls.target?. to get those happy.

Progress

• I chose a meaningful title that completes the sentence: "If applied, this PR will..."
• The implementation is complete.
• Pytests have been added (or are not necessary).
• Documentation has been added (or is not necessary).

Issue: Some controls don't work properly. Do we want to drop them and release the working ones first, or spend more time get them working?

Test script:

control_types = [
    ('Orbit controls (default)', None),  # Before the PR
    ('Arcball controls', 'arcball'),
    ('Trackball controls', 'trackball'),
    ('Map controls', 'map'),
    ('Fly controls', 'fly'),
    ('First-person controls', 'first-person'),
    ('Pointer lock controls', 'pointer-lock'),
]

for label, control_type in control_types:
    ui.label(label)
    with ui.scene(width=285, height=220, **({'control_type': control_type} if control_type else {})) as scene:
        scene.sphere()
        scene.move_camera(x=1, y=-1, z=1.5)

We have decided to ship the working ones.

• WORKING: Orbit controls: Working
• Arcball controls: Has a tendency to jump around sproadically
• WORKING: Trackball controls: Working
• WORKING: Map controls: Working
• Fly controls: Cannot control direction
• First-person controls: Cannot control direction
• Pointer lock controls: Cannot move camera

---

Feature request: #3710

[evnchn]

Tests are failing https://github.com/evnchn/nicegui/actions/runs/15367841581

[falkoschindler]

Wow, I didn't know that there are so many controls! Map controls seem to be very useful for 3D maps in RoSys!

Anyway, I don't think we need all of them at once. If this PR can get some of them to work and lay the foundation for adding more of them later, this would be just fine.

Regarding the implementation: Do we really need to import them in an async mounted() method? I'm not sure if making this method async could have unwanted side effects. But I guess you don't want to fetch all controls at once, but only the one which is needed.

[evnchn]

Do we really need to import them in an async mounted() method? I'm not sure if making this method async could have unwanted side effects.

Yes there were unwanted side effects: Failing tests and broken ui.scene_view()

Since three.js is so much larger in comparison to the controls, it isn't worth it to investigate in dynamically loading just the control we are using IMO. If you think you can do it, feel free to take a shot.

So far, only TrackballControls and MapControls work flawlessly, so those are the two I included in this PR.

Ready for review IMO.