Allow the backend builder role to have lambda:GetFunctionUrlConfig permissions

### Amplify CLI Version

10.5.1

### Question

To handle a stripe callback I need to expose an endpoint that can be called without authorization.
So I changed the Cloud formation template of the amplify function to include the URL config and permissions to allow such behavior. To my surprise the build failed because the amplify role doesn't have those permissions by default. Any particular reason? Am I doing something wrong with this approach?
In the mean time I-just created a new policy and attached it to the role with all the required permissions.
Thanks.

The issue identifies the CloudFormation template for the Amplify function and the backend builder role; start by locating where that role's IAM permissions are generated and reproduce the build with a Lambda function URL configuration. Done means the generated role permits lambda:GetFunctionUrlConfig and the build completes without a manually attached policy.

Written by the indexing model from the issue text.