Bridge filament basic render infrastructure

[hannojg]

Changes

• The EngineWrapper is creating all of the components we need for any scene to render (renderer, scene, view. camera, camera manipulator, swap chain, link to choreographer)
• The JS layer is creating an EngineWrapper and linking it with the surface
• The user can set a render callback
• The engine provides getters for all internal state to update it e.g. in the render

Example
We can't see anything yet but the basic render infrastructure is there in FilamentView.tsx

    // Get Surface:
    const fView = FilamentProxy.findFilamentView(this.handle)
    const surfaceProvider = fView.getSurfaceProvider()

    // Create engine and link it to the surface:
    const engine = FilamentProxy.createEngine()
    engine.setSurfaceProvider(surfaceProvider)

    // Callback for rendering every frame
    engine.setRenderCallback(() => {
      engine.getCamera().lookAt(engine.getCameraManipulator())
    })

Note:

Android will crash once start rendering, as it can't render anything without any entities in the scene (not sure why its not an issue on iOS though)

[mrousavy]

this.choreographer.addOnFrameListener((timestamp) => {
  // ...
})

Make sure to keep a reference on the returned listener, otherwise it might be destroyed I think? Not sure about that.

const listener = this.choreographer.addOnFrameListener((timestamp) => {
  // ...
})

// .. later

listener.remove()

We can also change the implementation of Listener to not remove itself when it is garbage collected, then it will only remove the listener if the parent (in this case Choreographer) is collected.

[mrousavy]

looks pretty good - left some comments!

[mrousavy]

we need to think about this as well - I see this a lot in your code where we do set(get->get()) which might be a bit unsafe.

[mrousavy]

for now its fine