Updated to Lombok based annotation

[apurbo290]

Updated to Lombok annotation based Getters and all arg constructor

[joicemjoseph]

Thoughts:
Lombok adds some friction:

1. every developer needs to set it up in their IDE
2. there's a learning curve for anyone new to it
3. debugging gets trickier since the generated code is invisible
4. and you're taking on another dependency to maintain.

[iamd3vil]

The better approach might be to use Java records instead of adding Lombok as a dependency. That will reduce the boilerplate without the need to take on this dependency.

[apurbo290]

POV:

1. Regarding another dependency to be maintained - Totally agree, though thoughts differ in Enterprises and maintainers, my thoughts: we should introduce Lombok if repo has future scope and has private artifacts in place.
2. Regarding Records: If not expecting mutable objs in future as well, my thought also the same.

Thanks!!