* Add concurrent tests

* Add missing 100x to a test's name

* Remove 100MiB file and generate file instead.

* See if using UUID for filename fixes this possibly-concurrency-issue.

* Try temporaryDirectory property.

* Fix concurrency issue

* Comment fixes & remove STS getCallerIdentity concurrent calls.

* Remove unused import

* Remove concurrent test for event stream output

* Refactor tests a bit

* Use FileStream to write to file

* Swap out filemanager with writing emtpy data approach

* Tweak a bit

* Simplify; no need to safe generated dummy data to a file, just use 50MB memory.

* Change from 10x50MB to 100x5MB

* Reduce payload from 5MB to 3MB

* Reduce payload from 3MB to 1MB.

* Add test for 1.5 MB to test aws chunked & flexible checksum flow also.

---------

Co-authored-by: Sichan Yoo <chanyoo@amazon.com>
Co-authored-by: Josh Elkins <jbelkins@users.noreply.github.com>

* Add features struct and feature struct for grabbing info we need from build request and feature to service name mapping JSON files.

* Add service feature & service documentation sections to release notes generation. Also, refactor it for consistent spacing between the lines even when sections are omitted.

* Update existing code that uses ReleaseNotesBuilder to reflect new changes.

* Update test that fails; possibly from previous package manifest change.

* Add regression tests for release notes builder.

* Only build service client sections in release notes if the repo is aws-sdk-swift.

* Add test flag (grr) to ReleaseNotesBuilder to allow tests. In real scenarios the JSON files we need are located in parent directory of aws-sdk-swift, but due to sandboxing, we can't save the dummy files to parent directory and instead can only save it in current directory. Use the flag to differentiate the path to retrieve JSON files from.

* Resolve Josh's PR comments

* Temporarily comment out repo has change check for running E2E test.

* Uncomment temporarily commented logic for generating empty manfiest if repo has no changes.

* Change SDK changes section name from AWS SDK for Swift to Miscellaneous & change commit filter criteria from discaring chore and Update, to including feat and fix.

---------

Co-authored-by: Sichan Yoo <chanyoo@amazon.com>

This reverts commit bfb7379.

* Add features struct and feature struct for grabbing info we need from build request and feature to service name mapping JSON files.

* Add service feature & service documentation sections to release notes generation. Also, refactor it for consistent spacing between the lines even when sections are omitted.

* Update existing code that uses ReleaseNotesBuilder to reflect new changes.

* Update test that fails; possibly from previous package manifest change.

* Add regression tests for release notes builder.

* Only build service client sections in release notes if the repo is aws-sdk-swift.

* Add test flag (grr) to ReleaseNotesBuilder to allow tests. In real scenarios the JSON files we need are located in parent directory of aws-sdk-swift, but due to sandboxing, we can't save the dummy files to parent directory and instead can only save it in current directory. Use the flag to differentiate the path to retrieve JSON files from.

* Resolve Josh's PR comments

* Temporarily comment out repo has change check for running E2E test.

* Uncomment temporarily commented logic for generating empty manfiest if repo has no changes.

* Change SDK changes section name from AWS SDK for Swift to Miscellaneous & change commit filter criteria from discaring chore and Update, to including feat and fix.

* Handle null value for releaseNotes and add test for it.

* Temporarily disable diff checker for running E2E tests

* Uncomment temporarily commented out diff logic.

---------

Co-authored-by: Sichan Yoo <chanyoo@amazon.com>

Co-authored-by: Sichan Yoo <chanyoo@amazon.com>

)

Co-authored-by: Sichan Yoo <chanyoo@amazon.com>

Co-authored-by: Sichan Yoo <chanyoo@amazon.com>