QML over HTTP server

[NeonDaniel]

When QML resources are served via HTTP paths (and possibly any non-file:// path), a special qmldir file is expected to exist for relative-path file resolution.

One potential option for Docker would be to bind the served resource directory to the host where the GUI client runs and translate paths to the host path (similar logic to how we currently translate paths to served URLs).

Alternatively, we just need to ensure that qmldir exists and is defined or else log some warning.

There may be other limitations to non-local resources for Qt and other GUI infrastructures to consider.

[mikejgray]

Worth calling out - if you aren't directly rendering JSX (which you shouldn't), the files need to be accessible to the web server. That probably means a lightweight Flask or FastAPI service from which the files can be retrieved.