[Feature] Eager services

[mproch]

EagerService + ServiceInvoker can be used to create service objects using fixed parameters.
Lifecycle is handled on the level of "main" EagerService.
TODO: cleanup, refactor of ServiceQuery

[arkadius]

1. Can we deprecate ServiceReturningType (with recommended migration to EagerService + ReturningType) in this change?
2. Also maybe it is also good time to deprecate WithExplicitMethodToInvoke.returnType and ServiceWithExplicitMethod? Because IMO better way now is to implement EagerService with WithExplicitMethodToInvoke returning ServiceInvoker with ReturningType - this approach has no limitation that user can't use eager parameters during compuation of returnType

[mproch]

1. Can we deprecate ServiceReturningType (with recommended migration to EagerService + ReturningType) in this change?
   True, I added deprecation
2. Also maybe it is also good time to deprecate WithExplicitMethodToInvoke.returnType and ServiceWithExplicitMethod? Because IMO better way now is to implement EagerService with WithExplicitMethodToInvoke returning ServiceInvoker with ReturningType - this approach has no limitation that user can't use eager parameters during compuation of returnType

Here I would like to refactor it a bit in next PR. I believe ServiceWithExplicitMethod would still be valuable, but it should be a helper function which implements stuff with GenericNodeTransformation