Variety of Improvements to deployment process

[HmSebastianH]

In the scope of a university assignment I took up the task to analyze and improve on the concept of lambdafication using annotations.

This Pullrequest contains multiple improvements to the termite tool:

• Added static code analyzing to look up dependencies of annotated methods and provide them in the deployment project
• This reduces size of generated project sources
  • It allows project classes to be used as input or output types of the lambda-functions
• Dispatched methods now wait for the return value (AsyncLambda.dispatch can be used if async handling is preferred)
• Methods are now properly supported by copying full context of the lambda function
  • allows usage of "this" variable and other class context
  • the self reference is implicitly added as first parameter for non static methods
• fixed multiple small issues

Known Issues:

• The local execution fallback sometimes seems to trigger another attempt at remote execution. This is caused by a AspectJ Bug which is documented here:
  AspectJ around aspect called twice when using a Mockito Spy spring-projects/spring-framework#24046
• The maven compile job triggers the plugin twice, this inflates the compilation time by a lot because all uploads are triggered twice. This could be solved by storing a hash of uploaded functions and comparing it before triggering a upload.