Fix introspection over ScannedGenericBeanDefinition

Resolves #420

Ensured that we check for the output type and see if and what type of conversion needs to be applied. If output is already a message with payload byte[], then no conversion is necessary

Resolves #419

polish

- added 'discoverFunctionTypeFromFunctionalObject' method to FunctionTypeUtils
- added tests to reproduce and validate the issue

Don't assume function is a bean

Fixes #412

Resolves #395

* Fix spring-integration sample

* Added discoverFunctionTypeFromClass() method to FunctionTypeUtils

* A `FactoryBean` may produce a function instance as well.
Add a logic into `BeanFactoryAwareFunctionRegistry` to discover a function type from the `FactoryBean.getObjectType()`

Migrate away from deprecated Spring Boot configuration property
bean classes and methods.
Resolves #410

Fixed discovery of functions to ensure that even in cases where default function is found but it's type can not be determined such function is discarded. This effectively ensures that if the actual instance does not match the declared type such function is not treated as function.

Resolves #409

- Added initial support for communicating routing instructions via SpEL thru both message headers and application properties
- Added support for communication function definition via application properties
- Added additional tests and updated documentation

Resolves #408

Added FunctionRegistration for each Kotlin lambdas with the correct types
Resolve #364

- Update versions of aws-lambda-java-core to 1.2.0, aws-lambda-java-events to 2.2.6 and aws-java-sdk-s3 to 1.11.557

Resolves #373

Resolves #381