[stepfunctions] nextToken should not be required in output type

[taesungh]

Similar to #238, the type definitions for the responses of some of the methods on the AWS Step Functions client specify nextToken as required in the TypedDict when it is not always returned.

For example, here is GetExecutionHistoryOutputTypeDef (for get_execution_history)

GetExecutionHistoryOutputTypeDef = TypedDict(
    "GetExecutionHistoryOutputTypeDef",
    {
        "events": List["HistoryEventTypeDef"],
        "nextToken": str,
        "ResponseMetadata": "ResponseMetadataTypeDef",
    },
)

and this also applies to ListExecutionsOutputTypeDef and a few other output types

Example query and response

There may be multiple pages for execution history,

import boto3
sfn_client = boto3.client("stepfunctions")
history = sfn_client.get_execution_history(executionArn="arn:...")

but the response doesn't include nextToken when there are no more pages.

{
    "events": [
        { ... },
    ],
    "ResponseMetadata": { ... },
}

Additional context

Referencing mypy-boto3-stepfunctions v1.35.9

[vemel]

Hello! Thank you for the report.

I already have a list of keys that should not be marked as required in output shapes. I can mark nextToken as Optional as well. I will check how many services are affected.

As far as I know, botocore team tries to follow the same pagination pattern for all services, but we will see.

[vemel]

Actually, as I see NextToken is already marked as NotRequired, but nextToken is not :) So, not all services follow the same pagination pattern.

[vemel]

Fixed in mypy-boto3-builder 8.1.3. Also, I released mypy-boto3-stepfunctions 1.35.46 with the fix included. Please update and let me know if it works as expected.