<!-- Love localstack? Please consider supporting our collective:
👉  https://opencollective.com/localstack/donate -->

# Type of request: This is a ...

[ ] bug report
[X ] feature request

# Detailed description

I'm using localstack to create a dynamoDb table locally with a dynamodb stream and a flink application consuming data from the stream
The shardId created in localstack follows this format

shardId-000000000000-798cedd84a2953c5af70a131f8701f35

Flink expects this format
shardId-00000001592367572726-07776efd

The difference is just after the prefix shardId.
Normally the real shardId created by amazon use is composed by shardId prefix, 20-digit timestamp and 0-36 or more characters separated by '-'

The current shardId format is not valid for flink applications and it's not following the real pattern used by amazon

## Expected behavior

ShardId must follow the pattern
shardId prefix, 20-digit timestamp and 0-36 or more characters separated by '-'

## Actual behavior

The shardId follows the pattern
shardId prefix, 12 0s and 33 characters separated by '-'

# Steps to reproduce

Create a dynamodb table

## Command used to start LocalStack

I'm using docker and docker compose to run localstack


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

aws --endpoint-url=http://localhost:4566 dynamodb create-table \
    --table-name temp4 \
    --attribute-definitions AttributeName=partition_key,AttributeType=S AttributeName=sort_key,AttributeType=S \
    --key-schema AttributeName=partition_key,KeyType=HASH AttributeName=sort_key,KeyType=RANGE \
    --provisioned-throughput ReadCapacityUnits=100,WriteCapacityUnits=100 \
    --stream-specification StreamEnabled=true,StreamViewType=NEW_AND_OLD_IMAGES


if not is_local_mount or not use_docker() or config.LAMBDA_REMOTE_DOCKER:
                file_list = run('cd "%s"; du -d 3 .' % lambda_cwd)
                config_debug = ('Config for local mount, docker, remote: "%s", "%s", "%s"' %
                    (is_local_mount, use_docker(), config.LAMBDA_REMOTE_DOCKER))
                LOG.debug('Lambda archive content:\n%s' % file_list)
                raise ClientError(error_response(
                    'Unable to find handler script (%s) in Lambda archive. %s' % (main_file, config_debug),
                    400, error_type='ValidationError'))
        if runtime.startswith('python') and not use_docker():
            try:
                
                ensure_readable(main_file)
                zip_file_content = load_file(main_file, mode='rb')
                
                lambda_handler = exec_lambda_code(
                    zip_file_content,
                    handler_function=handler_function,
                    lambda_cwd=lambda_cwd,
                    lambda_env=lambda_environment)
            except Exception as e:
                raise ClientError('Unable to get handler function from lambda code.', e)
    add_function_mapping(lambda_name, lambda_handler, lambda_cwd)
    return {'FunctionName': lambda_name}
def do_list_functions():
    funcs = []
    this_region = aws_stack.get_region()
    for f_arn, func in arn_to_lambda.items():
        if type(func) != LambdaFunction:
            continue