fix: remove target prop type in controls where it isn't applicable

[jure]

Why

After looking at various controls during (#285) I noticed they all have target specified in their types. Only three actually need it/can use it on the Three.js side: OrbitControls, TrackballControls and MapControls (which is OrbitControls underneath).

What

Removes prop types where they are not applicable/are misplaced. For PointerLockControls, this fix is handled in #285.

Checklist

• Ready to be merged

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/pmndrs/drei/r3tj098k9
✅ Preview: https://drei-git-fork-jure-fixextrapropfields.pmndrs.vercel.app

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 5a657e7:

Sandbox	Source
inspiring-mendel-2yfw6	Configuration
drei reflector	Configuration

[joshuaellis]

There's a fix on beta for ESM modules that I need to check this evening, so I'm gonna merge them into beta first. I have no doubt that you're code works though 🦖

[github-actions]

🎉 This PR is included in version 3.2.3-beta.2 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This PR is included in version 3.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀