execution_id_prefix separates global uniqueness from executing unit

Whether a task is (domain) global unique is determined by execution id.
Where the task is processed is (still) determined by its unit.

This way, different units (read: applications in different historical
states) may still be used to process only their "own tasks", but an
execution can be unique among all of them.

Closes #7
Doc tuning
Move method to single remaining usage
Refactoring
Renamed new method
Version 2.0.6
allow additional tags for workflow execution
Merge pull request #10 from infopark/feature-workflow-tags

allow additional tags for workflow execution
Make licence spec conform to standard
Provide error abstraction

Most basic implementation for SWF using aliases.
Fix # 4
Abstract runtime errors

Fix #4
v 2.0.8
Merge pull request #13 from dcsaszar/master

Error abstraction
inject swf dependency, deprecate usage of aws credentials
v 2.0.9
require rspec 2
Merge pull request #14 from infopark/feature-remove-credentials

Feature remove credentials
Typo and doc fix
Use master-workflow and master-activity types by default

The types are equal on all systems, so no need to duplicate
task_list_suffix_file becomes isolation_file

It will now be prepended to task list names and execution IDs.
Fixes #11