fix(provider-generator): rename lambda namespace in lambda functions

[DanielMSchmidt]

In python this lead a problem with importing this aws resource

Closes #1152

[ansgarm]

Naming is fine with me as all resources belonging to the AWS Lambda Service are geared around Lambda Functions.

@skorfmann fine with you as well?

[skorfmann]

Naming is fine with me as all resources belonging to the AWS Lambda Service are geared around Lambda Functions.

Hm, the naming is a bit confusing.

Just rename for python using feat: allow per-submodule naming configuration aws/jsii#1690

Have you looked into the 2nd option mentioned by @jsteinich?

[DanielMSchmidt]

Hm, the naming is a bit confusing.

I'm open for suggestions :)

Have you looked into the 2nd option mentioned by @jsteinich?

I just took a look in rename-lambda-functions-for-use-in-python-only, I'm unsure how to get this working 🤔

[skorfmann]

Thought a bit about it, and LambdaFunction seems to be the best way right now. Per language renaming would lead to confusion in documentation and similar places. Also, haven't found a better name.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.