Showcase External r3f components on docs

[jo-chemla]

I've never come across an up-to-date list of r3f components created by contributors outside of the pmndrs org - something along the lines of awesome-react-three-fiber, whose last update is 3yo. Would it make sense to showcase interesting and re-usable r3f components created outside of the pmndrs org somewhere in the docs? It could probably be located under the Getting started section.

This could include from the top of my mind:

• utsuboco/r3f-perf
• FarazzShaikh/THREE-CustomShaderMaterial
• Luma Labs Gaussian Splats renderer
• NASA-AMMOS/3DTilesRendererJS (r3f wip readme)
• Looking Glass
• spite/THREE.MeshLine
• Theatre-js
• NYTimes/three-loader-3dtiles

Plus these ones I discovered searching:

• ektogamat/R3F-Ultimate-Lens-Flare
• troika-three-text

Regarding citation of existing pmndrs wrappers for projects of external contributors like gkjohnson three-mesh-bvh/Bvh or three-gpu-pathtracer/pmndrs/react-three-gpu-pathtracer component, these are already in the drei doc, so probably no need to add them to this list.

I can come up with a quick PR if this is deemed to make sense!

[jo-chemla]

Just made a PR here: #3378 🎉
Demo is visible here:

[jo-chemla]

Two final notes:

• I've edited images so they have the same aspect ratio than codesanboxes screenshots. I've tried to do it in markdown but only solution I found was to pass to <Img> components the props className="aspect-[16/9] object-cover" width="1763" height="926"
• I've spotted the fetchCSB function that is applied here. and I am assuming this props merging should be the other way around: const merged = { ...data, ...props } so user-provided props do not get replaced by those returned by the codesandbox API calls, like eg screenshot_url - if the user pass it to the Codesandbox component, then it should not be overwritten by the api call. Should I push a quickfix PR for this?

This doc update is ready to merge from my point-of-view!