Unable to set lambda invoke timeout

**Describe the bug**

When executing long running lambda synchronously via ADO, the task uses the default botocore timeout of 60s. This causes the lambda to be invoked several times as it doesn't wait for the first invocation to finish.

**To reproduce**

Create a lambda which runs for more than 60s. Execute it via ADO and check the lambda execution logs in CloudWatch. 2 executions will be listed even though the first one finishes successfully

**Expected behavior**

The Lambda Invoke task should retrieve the timeout defined in the Lambda and use that as the execution timeout

**Your Environment**
- Azure DevOps Cloud
- AWS Toolkit for Azure DevOps version: aws-cli/1.18.66

Task : AWS Lambda Invoke Function
Description : Invokes an AWS Lambda function
Version : 1.7.0

Start by locating the AWS Lambda Invoke Function task and the code that configures its botocore or AWS SDK invocation timeout. Reproduce with a Lambda running longer than 60 seconds and inspect its CloudWatch logs; done means one synchronous invocation waits for the configured Lambda timeout instead of invoking the function again.

Written by the indexing model from the issue text.