StartExecutionManager fails to invoke worker if jobs exceed Lambda payload size limit

[jtherrmann]

Jira: https://asfdaac.atlassian.net/browse/TOOL-3344

Note: The above link is accessible only to members of ASF.

---

StartExecutionManager fails to invoke the worker function if the batch of jobs exceeds the Lambda payload size limit:

[ERROR]	2024-12-06T20:44:44.763Z	99a0084a-4074-4b29-87d6-19e0ad896161	Unhandled exception
Traceback (most recent call last):
  File "/var/task/lambda_logging/__init__.py", line 18, in wrapper
    lambda_handler(event, context)
  File "/var/task/start_execution_manager.py", line 35, in lambda_handler
    response = invoke_worker(worker_function_arn, jobs)
  File "/var/task/start_execution_manager.py", line 16, in invoke_worker
    return LAMBDA_CLIENT.invoke(
  File "/var/task/botocore/client.py", line 569, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/var/task/botocore/client.py", line 1023, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (RequestEntityTooLargeException) when calling the Invoke operation: 334391 byte payload is too large for the Event invocation type (limit 262144 bytes)

This is consistent with https://docs.aws.amazon.com/lambda/latest/dg/gettingstarted-limits.html which shows "256 KB (asynchronous)" for "Invocation payload".

@asjohnston-asf points out that we may no longer have any requirement for the throughput increase granted by the manager/worker model. We'll have to discuss further.

Relates to #1272