Remove Init() methods from Framework and Processes

Using separate Init() methods for initialization (instead of initializing in the constructor) goes against RAII design practices (see the link for a long list of reasons why separating construction from initialization is generally a bad idea). See #214 (closed) and the discussion in !158 (closed) by H. Dembinski.

Furthermore, the usage of Init() was not uniform (or documented). Some classes had no-op constructors and mandatory Init() while others had initializing constructors and no-op Init() (and some had both!).

This MR moves the contents of Init() methods into the constructor so that the constructor performs all required initialization. (No other code improvements or cleanup was performed). This is the first (baby) step in moving C8 to being fully RAII-compliant.