Reduce depth of GH workflows used #293
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:

The depth of GH workflows invoked is exceeding 3 and fails for build-and-upload-integration.yml
Description of changes:
The current flow calls:
build-and-upload-integration
->build-and-upload-release
->build-and-upload
->application-signals-e2e-test
->aws-observability/aws-application-signals-test-framework/.github/workflows/python-eks-test
.The new flow eliminates calling
build-and-upload-release
and now calls:build-and-upload-integration
->build-and-upload
->application-signals-e2e-test
->aws-observability/aws-application-signals-test-framework/.github/workflows/python-eks-test
.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.