Remove Jobs from Services #35
Description
This is a composite issue: There will be specific issues for each Job, so that they may be tracked as each is completed.
A service is/should be a set of functionality that is (typically openly) available for clients and consumers to use. In the circumstance of JobsService, it is combined with several other (current) services that are simply tasks performed at specific intervals. The list includes RssService, Leaderboards Service and StreamsService.
There is little reason to keep these available as a Service as they completely encapsulate their work process. In fact, they are more cleanly defined as Workers rather than Services. Redefining them as Workers, rather than Services will allow more SOLID architecture, cleaner instancing, lighter memory usage, and better reporting. It will also facilitate looser coupling, testing/mocking, and will allow event-based processing. Finally, it will accommodate issues similar to #30 and #31 much more easily.