<!-- 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
* Define a lambda function in a CDK stack (e.g. "TestStack"), giving it a descriptive ID value (e.g. "DescriptiveName")
* Deploy the CDK template (`cdklocal deploy`)
* Check the function's name in the dashboard

## Expected behavior
Function's name includes its CDK stack ID. For example, deploying the template to AWS will produce a function name of the form `<StackName>-<FunctionID><mishmash>` (e.g. TestStack-DescriptiveName8C62FF46-hXye7CyPgrc7)

## Actual behavior
Function's name has the form `<StackName>-lambda-<mishmash>` (e.g. TestStack-lambda-cb0e840d), making it more difficult to use in the localstack dashboard when there are several lambdas.

# Steps to reproduce
See detailed description

## Command used to start LocalStack
`LOCALSTACK_API_KEY=... localstack start`

## Client code (AWS SDK code snippet, or sequence of "awslocal" commands)
(none)
),
                },
                "defaults": {
                    "ProvisionedThroughput": {
                        "ReadCapacityUnits": 5,
                        "WriteCapacityUnits": 5,
                    }
                },
            },
            {
                "function": "enable_kinesis_streaming_destination",
                "parameters": get_ddb_kinesis_stream_specification,
            },
        ],
        "delete": {
            "function": "delete_table",
            "parameters": {"TableName": "TableName"},
        },
    },
    "IAM::Role": {
        "create": {
            "function": "create_role",
            "parameters": param_defaults(
                dump_json_params(
                    select_parameters(
                        "Path",
                        "RoleName",
                        "AssumeRolePolicyDocument",
                        "Description",
                        "MaxSessionDuration",