Wrong amplify.state references nodejs runtime instead of python for lambda functions

[maunzCache]

Describe the bug
A few lambda functions located in amplify/backend/function/ reference in their amplify.state file a nodejs provider but are actually python functions. See amplify/backend/function/teamgetPermissions/amplify.state for example

To Reproduce

Expected behavior
The amplify.state files are aligned with the actual codebase.

Additional context
Might not be relevant for a deployment but will surely backfire on local development such as running amplify mock.

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed.

[maunzCache]

Still present

[github-actions]

Marking this issue as stale due to inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed.

[maunzCache]

Will drop the PR if i don't get any response @tawoyinfa . I know maintining a project is a lot of work. But i don't want to get a notification all 30 days anymore, that the issue is going to be closed.