Remove Lombok usage in favour of Immutables

[JaidenAshmore]

Lombok has the disadvantage when developers look at the source files of the library that they get a big warning about the source file not matching the actual code. I am mostly using Lombok for POJOs and builders which can be replaced with Immutables Java which auto generates implementations. Some functionality like @slf4j, @UtilityClass are lost but that is not a big deal at all. Losing @DeleGate sucks but it will just be one conversion effort to replace that.

[mistriel]

Totally disagree on that one.
Lombok has the advantage of reducing boiler print code. I'm using IntelliJ along with Lombok plugin and Annotation processing - no warnings what so ever.