Refactor the Naming Conventions

Right now, the naming conventions between fragments, Dagger modules, actions, middleware, and reducers really aren't consistent. These entities should be named consistency so that an engineer and understand the logical "buckets" that they relate to.

Here are some thoughts:

• Give a fragment a name (such as LoginFragment) and ensure that the relevant action, middleware, reducer, and dagger module has the same name (LoginFragment, LoginAction, LoginMiddleware, LoginReducer, LoginModule, LoginComponent)
• Use a similar convention for Routing (RoutingAction, RoutingModule, etc...) and Authentication (all things related to Auth0, such as session and profile management)

This should help naming stay more across packages.