Asgard-1165 - Better double form submission prevention

Correctly handles both the cases of regular form and jQuery validate form
Activity Type list screen
ActivityTypeController remove RegionAgnostic
Completed workflow executions list
Workflow domain cache and list in progress
ASGARD-959 - Ensure workflow domain gets created, with undiscoverable, read-only list and show domain screens
Add open workflow executions list
Fix ListOpenWorkflowExecution call
Display open workflow executions
Workflow types list
Read only views of SWF objects
AWS Flow framework helper utilities
retrofit Tasks to work with SWF
temporarily removing deployment workflow references
Better spinner image for light grey backgrounds
Make submit buttons look unclickable
ASGARD-1174 - Init screen on Firefox should not do infinite redirects

It also should not show the loading screen when the administrator still hasn't configured Asgard yet.

Instead, Firefox should immediately show the message about why Firefox is currently incompatible.
Merge pull request #327 from joesondow/ASGARD-1174-Init-Firefox

ASGARD-1174 - Init screen on Firefox should not do infinite redirects
Asgard version 1.2 update with release notes
Merge pull request #335 from joesondow/ASGARD-1174-release-1.2

Asgard version 1.2 update with release notes
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.
removing CodeNarc violations
Use toggleClass instead of if-else
Better variable name
Merge pull request #326 from joesondow/ASGARD-1165-better-double-submit-prevention

Asgard-1165 Better double submit prevention