Delete, hand-off or migrate plugins out of if-unofficial-plugins

[jmcook1186]

Sub of: #656

User story

As a user I want to have minimal dependencies,packages and repositories to manage when I use IF. As a developer I want to be clear about what's in my remit to maintain and what is not.

Rationale

We currently maintain several repositories for plugins, which is sometimes a bit unwieldy. It's also not always clear to community contributors what the criteria are for inclusion in the different repositories (e.g. unofficial plugins is often interpreted as a public repository for community plugins, which was not the intention. These frictions can be reduced by moving plugins out of if-unofficial-plugins and either deleting them, moving them to builtins, moving them to if-plugins or handing them over to others to maintain. This ticket covers defining the right process for the deprecation of if-unofficial-plugins and making the necessary changes.

Implementation details

• examine the plugins in if-unofficial-plugins and propose an action for each (migrate, hand-off or delete)
• implement the actions for each plugin
• delete if-unofficial-plugins if possible
• update all documentation

Priority

3/5

Size

L

What does "done" look like?

if-unofficial-plugins is deleted tor exists in its minimal viable state.

Does this require updates to documentation or other materials??

yes, extensive updates are expected to all documentation

Deadline

tbc

[jmcook1186]

Blocked on the outcomes from #640 and #546