fix: check for script entry point even if setup.py is present

[ajaykarpur]

Issue #, if available: Fixes https://github.com/aws/sagemaker-training-toolkit/issues/75

Description of changes:

• If setup.py is present, the entry point is assumed to be a Python package even if the provided entry point is a shell script.
• This PR changes the entry point behavior by first checking for a .sh entry point file extension.

Testing done:

• Ran unit tests.

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

General

• [x] I have read the CONTRIBUTING doc
• [x] I used the commit message format described in CONTRIBUTING
• [ ] I have used the regional endpoint when creating S3 and/or STS clients (if appropriate)
• [ ] I have updated any necessary documentation, including READMEs

Tests

• [x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
• [ ] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[sagemaker-bot]

AWS CodeBuild CI Report

• CodeBuild project: sagemaker-training-toolkit-pr
• Commit ID: 5469e861a1b68e3bb1441fe652f98fc22e02765a
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository