Bridge plugin rewrite

[gdude2002]

Over time, the bridge plugin has become pretty nasty. It needs a rewrite - here's some points to look at for that.

• [ ] Configuration
  • The configuration has become really quite messy. I feel like we could redesign the entire thing.
  • We could have a directory of config files to load - Perhaps we could add a Directory type to the storage manager that can load all the files from a directory up into an array or something
• [ ] Modularity
  • It became apparent pretty quickly that this was going to need to support a bunch of events from all over the place. Therefore, we should split bridge up into modules that can be added to by other plugins.
  • As a "standard" plugin, I don't really see any reason plugins and protocols can't just throw .py files into a directory, but it would probably be better to have them register or something. Needs thought.

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/8066775-bridge-plugin-rewrite?utm_campaign=plugin&utm_content=tracker%2F269930&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F269930&utm_medium=issues&utm_source=github).

[gdude2002]

@rakiru Should we have protocols register their own handlers for Bridge? It feels like that might be the most sensible way.