### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current Behavior

When I fetch execution history via command below, it always returns history events in ascending order.

`awslocal stepfunctions --region eu-west-1 get-execution-history  --reverse-order --execution-arn <execution-arn> `

I also tried with 

``awslocal stepfunctions --region eu-west-1 get-execution-history  --no-reverse-order --execution-arn <execution-arn> `

it returned the same results, which proves again that `--reverse-order` didn't take effect.

I also tried with `GetExecutionHistoryCommand` from `@aws-sdk/client-sfn`, it's the same results that reverse order didn't take effect.

it seems that `PROVIDER_OVERRIDE_STEPFUNCTIONS=v2` will cause this issue, and it's set to be v2 by default in localstack v3. but if I set it back to `PROVIDER_OVERRIDE_STEPFUNCTIONS=legacy` and use loacalstack v2, then this problem won't appear anymore.

### Expected Behavior

when `--reverse-order` is provided. Execution history is returned in descending order. Also, command sent from sdk should see the same results.

### How are you starting LocalStack?

With a docker-compose file

### Steps To Reproduce

#### How are you starting localstack (e.g., `bin/localstack` command, arguments, or `docker-compose.yml`)

    docker compose -f docker-compose.yml up -d

#### Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)

    awslocal stepfunctions --region eu-west-1 get-execution-history  --reverse-order --execution-arn <execution-arn> 


### Environment

```markdown
- OS: macOS 14.1.1
- LocalStack: I tried both v3.0 and v3.0.2, neither of them worked. But v2.1 worked.
```


### Anything else?

_No response_
with pytest.raises(Exception) as err:
            aws_client.stepfunctions.start_execution(
                stateMachineArn=state_machine_arn, input="not some json"
            )
        sfn_snapshot.match("start_exec_str_inp", err.value.response)
        with pytest.raises(Exception) as err:
            aws_client.stepfunctions.start_execution(
                stateMachineArn=state_machine_arn, input="{'not': 'json'"
            )
        sfn_snapshot.match("start_exec_not_json_inp", err.value.response)
        with pytest.raises(Exception) as err:
            aws_client.stepfunctions.start_execution(stateMachineArn=state_machine_arn, input="")
        sfn_snapshot.match("start_res_empty", err.value.response)
        start_res_num = aws_client.stepfunctions.start_execution(
            stateMachineArn=state_machine_arn, input="2"
        )
        sfn_snapshot.add_transformer(sfn_snapshot.transform.sfn_sm_exec_arn(start_res_num, 0))
        sfn_snapshot.match("start_res_num", start_res_num)
        start_res_str = aws_client.stepfunctions.start_execution(
            stateMachineArn=state_machine_arn, input='"some text"'
        )
        sfn_snapshot.add_transformer(sfn_snapshot.transform.sfn_sm_exec_arn(start_res_str, 1))
        sfn_snapshot.match("start_res_str", start_res_str)
        start_res_null = aws_client.stepfunctions.start_execution(
            stateMachineArn=state_machine_arn, input="null"
        )
        sfn_snapshot.add_transformer(sfn_snapshot.transform.sfn_sm_exec_arn(start_res_null, 2))
        sfn_snapshot.match("start_res_null", start_res_null)
    @markers.aws.validated
    def test_stop_execution(