renamed workflow log to status to make Grails happy
I'm not sure why it saw the workflow as being injected with a Grails logger.
AWS clients are expected to have this constructor via reflection
Reducing unit tests that ensure that AWS Flow objects are constructed correctly.
There are basic AWS Flow objects that cannot even be constructed without a global variable being set (AsyncContextBase.currentContext).
In order to set it I need to create an AsyncParentContext, but since it is private I get errors like "cannot access its superinterface com.amazonaws.services.simpleworkflow.flow.core.AsyncParentContext".
If AsyncParentContext was simply made public then these problems would disappear.
renamed test to work around Grails magic
Grails insists on calling afterPropertiesSet() on the service.