Issues/23: Enable Harmony write output to user bucket

[frankinspace]

Github Issue:

#23 Harmony requests now include destinationUrl parameter to place output directly in s3 bucket instead of requiring data to be copied.

Also addressed

#9 Added some documentation for installing as cumulus module
#41 Module no longer depends on deprecated hashicorp/template provider
#42 Terraform version upgraded to v1.5.3

Description

Module will now allow Harmony to write output to a staging bucket directly instead of copying data from Harmony.

Overview of work done

• Added new module variable bignbit_staging_bucket. If left blank a new S3 bucket will be created with permissions for Harmony to write output to the bucket and GIBS to read from the bucket.
• Replaced copy to s3 lambda function with new process harmony results lambda function
• Move lambda role creation to within the module instead of needing to be declared externally and passed as variable.
• Updated readme with better installation instructions
• Removed deprecated hashicorp/template provider
• Upgraded terraform to v1.5.3

Overview of verification done

Deployed to SIT and successfully executed both OPERA HLS and S1 granules

Overview of integration done

Will test further in UAT with GIBS.

PR checklist:

• Linted
• Updated unit tests
• Updated changelog
• Integration testing

See Pull Request Review Checklist for pointers on reviewing this pull request