Add working directory to `sam invoke local`

[JadenSimon]

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)

Description

This should've fixed an issue with SAM CLI not detecting samconfig.toml for sam local invoke But apparently SAM CLI treats the template path as the project root. I think we can just get rid of using --template when provided by a user. Which would fix the issue (plus less opportunity for unexpected behavior).

Motivation and Context

Related Issue(s)

#3105

Testing

Screenshots (if appropriate)

Checklist

• [ ] I have read the README document
• [ ] I have read the CONTRIBUTING document
• [ ] Local run of gradlew check succeeds
• [ ] My code follows the code style of this project
• [ ] I have added tests to cover my changes
• [ ] All new and existing tests passed
• [ ] A short description of the change has been added to the CHANGELOG if change is customer facing in the IDE.

License

I confirm that my contribution is made under the terms of the Apache 2.0 license.

[sonarqubecloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[rli]

/runIntegrationTests

[JadenSimon]

SAM CLI recommends using --config-file (https://github.com/aws/aws-sam-cli/issues/3431) but if we're going to use that parameter then we should expose it in the UI.