fix: remove maxRetries because it does odd things

in testing this property changes behaviour in strange way
setting it seems to prevent errors from surfacing at all).
seems to be an issue with aws sdk.

src/createHandler.js

@@ -7,7 +7,6 @@ function createHandler(config) {
 		currentRegion,
 		awsEndpoint,
 		backoffSeconds = 30,
-		awsClientMaxRetries,
 		enabled = true,
 		// we split currentRegion from sqsRegion to solve https://github.com/localstack/localstack/issues/2982
 		sqsRegion = currentRegion,
@@ -19,7 +18,6 @@ function createHandler(config) {
 	const sqsClient = new SQS({
 		region: sqsRegion,
 		endpoint: awsEndpoint,
-		maxRetries: awsClientMaxRetries,
 	});
 
 	async function invokeHandler(handler, message, messageMetadata) {

test/createHandler.test.js

@@ -66,7 +66,7 @@ function nockReceiveError(queueUrl, times = 1) {
 			)}&Version=2012-11-05&VisibilityTimeout=30&WaitTimeSeconds=1`
 		)
 		.times(times)
-		.replyWithError('something awful happened');
+		.reply(400, 'eg bad queue url');
 	return {
 		scope,
 	};
@@ -262,8 +262,6 @@ tap.test('should backoff and resume for errors', (t) => {
 		backoffSeconds: 1,
 		longPollSeconds: 1,
 		currentRegion: 'us-east-1',
-		// otherwise we have to nock enough errors to get past the aws sdk's automatic retrying.
-		awsClientMaxRetries: 0,
 	});
 	let handlerCalls = 0;
 	handler.addQueueHandler(queueUrl, (msg) => {