feat: Remove plugins, i.e. move to community plugins repo

[lalalune]

Currently all of our plugins are kept in the main monorepo, but this is causing extreme dependency bloat.

We have a new repo here, which has all of the plugins:
https://github.com/elizaOS/community-plugins

This PR removes the plugins. Since the history is shared, we should be able to retarget plugin PRs to that repo.

[tomguluson92]

Ok, I just commit a new PR about plugin with TTS a few hours ago. Definitely support this move, A lite and concise core runtime is cool.

[odilitime]

Can we add some categorization around whether it's a service versus a plugin that any one can use without any API keys. Maybe even separate our partner plugins from the community ones.

[dev-cz]

Agree with @odilitime . Also extending that, like maybe its free with limited usage, but API key is paid, so like a Freemium tag or something as well.

I also think having some sort of commitment of support for X time, for it to be approved to merge in, because many plugins are created and the creator is gone, so further adds broken, plugins because than others create their own version.

[jmikedupont2]

also some plugins like solana chime in on evaluations even if they are not activated it seemed in the past, so we also want to be able to prevent them from accidentally being activated.

[odilitime]

superseded by #3339