File handling change and Trigger unique ID

Trigger - getUniqueTriggerID

request.js file now supports getUniqueTriggerID property, which should be a function. The arguments passed in (order) are params, http, and output (from the before function). The function is expected to return either a string or number, which would then be set as trigger_deduplication_id in the JSON headers property (NOT the HTTP header from the dev server during development).

File handling - AWS SDK migration

As of this version, the file handling has been migrated to use the AWS SDK instead of the Knox library. This therefore means that environment variables can now be utilised (including the use of roles for the lambda function).

Additionally, bucket and region can also now be passed in to override the default values of workflow-file-uploads and us-west-2 respectively.

NOTE: Unless environment variables are setup with AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY, local development will still need the aws.json file to be required.