Using dependency injection

[NotToDisturb]

Hello hello!
This issue is to open the discussion on dependency injection to simplify development

I've created a POC (NotToDisturb@e3cd9e6) using Dagger and Lombok, the tools I'm most familiar with.

The changes are not E2E, changed just enough to show the potential in terms of reducing dependency across classes, among other things.

Lombok also brings other benefits like:

• Less constructors by using the @RequiredArgsConstructor decorator (constructors with logic will still be needed)
• No longer needing to declare the logger (instead using the @Slf4j decorator)
• Not showcased here, but tags like @Builder, @Value, @Getter and @Setter simplify data class creation and more (I can publish a POC for this too)

Thoughts?

PS: Didn't create this as a PR as it would include the changes from #76

[kuroppoi]

I've actually never used dependency injection before and have no idea what it is so it looks like some sort of evil dark magic to me lol

[NotToDisturb]

Honestly when I started using it a bit ago it looked like dark magic too haha, but it's really cool.

The thing I ended up liking the most is that each class doesn't have to care about how to initialize an attribute, and allows for encapsulating that initialization better.

UserManager for instance, we create a Module in that provides a Singleton for UserManager, and Dagger injects it whenever a class asks for a UserManager instance, like here.

In this case, I set it up so the Entralinked Component depends on the Http, GameSpy and DnsServer Modules (server modules), and in each of them the necessary objects for those servers are created. Since some objects are needed in multiple servers (for instance, UserManager), I created the PersistentData Module, which is included in the server modules that need it.