feat(app): 680 UseTexture composable as component

[JaimeTorrealba]

closes #680

Convert a composable like this one, as a component is not difficult, what I would like to know is what do you think about this one

Component Name

Vueuse, use the same name of the composable and seems to have no problem (the component start with uppercase), but what do you think? Could this confuse users? Any other alternatives.

useTexture and UseTexture

    <Suspense>
      <UseTexture v-slot="{ map }" :map="path">
        <TresMesh>
          <TresBoxGeometry />
          <TresMeshStandardMaterial :map="map" />
        </TresMesh>
      </UseTexture>
    </Suspense>

Props and result

They share the same name in the example they are :map="map" and the result currently is v-slot="{ map}"

I personally don't see any problem but again I would like to know what do you think?

Docs

I would not do the docs just yet, until your answers. But my idea is to put the docs of this just below the existing composable, any thoughts?

[netlify]

✅ Deploy Preview for tresjs-docs ready!

Name	Link
🔨 Latest commit	3eb919e
🔍 Latest deploy log	https://app.netlify.com/sites/tresjs-docs/deploys/66daff9a37850600081fb19e
😎 Deploy Preview	https://deploy-preview-757--tresjs-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[alvarosabu]

Love the idea but not the execution. We need to be more strict on the standardization of the code base and avoid having 3 different approaches to components.

[pkg-pr-new]

Open in Stackblitz

pnpm add https://pkg.pr.new/@tresjs/core@757

commit: 3eb919e