Chore: Add a component registry object to make it easier to get and track singleton lifecycles #43
Description
To take a first step toward an IoC architecture, and to make it easier to wrangle our project state, we should introduce a single top-level component that serves as an object/component registry for long-lived objects that are used in cross-cutting ways such as the active config, the network client (e.g. RedisClient or RedisServer), and an eventual state manager.