Use protected methods for ActivityFactory instead of private

Currently the ActivityFactory has a lot of private methods. This makes extending the class very difficult because each private method will need to be reimplemented in an inheriting class. This leads to code duplication, hard maintenance and eventually bugs.

We already have an internal use-case for extending this class in the social_renamer module. I don't see a good reason to keep any of the methods private.