Untangle federation code, make ActivityPub and OStatus optional
At the moment, we have an on/off switch for federation, but it would be good to untangle Ostatus from ActivityPub federation code for a few reasons:
- Easier testing (I suspect we have some bugs in interaction with instances that are both OStatus and AP
- Better internal architecture by figuring out what the common functions are and what should be seperate modules
- Easier adding of additional federation mechanisms if we ever need them