Update the default location of the updated  AndroidManifest file
Use resolved project.build.finalName property

Currently we mostly use project.getBuild().getFinalName() to read the
property. Unfortunetely this can return an unresolved version of the
property if one uses multiple profiles and dynamic finalName (e.g. if
some plugins generate the finalName at Maven execution).

This commit resolves this issue by injecting the resolved
project.build.finalName property by @Parameter annotation, and using
that value everywhere.
added helloflashlight example project and a integration test that builds, deploys and runs the app
added morseflash app and IT test
fixed test invocation and added some relevant asserts
Merge pull request #461 from jayway/sampletests

Sampletests
Merge pull request #457 from Shusshu/manifest-update

Update the default location of the updated  AndroidManifest file
Merge pull request #460 from WonderCsabo/458_dynamicallyResolveFinalname

Use resolved project.build.finalName property