AWS::Lambda::Function retry throttled calls

## Scope of request

When bringing up a template with a bunch of Lambdas, it's not unusual to get this error message:

`Your request has been throttled by EC2, please make sure you have enough API rate limit. EC2 Error Code: RequestLimitExceeded. EC2 Error Message: Request limit exceeded. (Service: AWSLambdaInternal; Status Code: 400; Error Code: InvalidParameterValueException; Request ID: 9a25c9eb-0275-476f-82f3-9d7773ace5da; Proxy: null)`

When this happens, retrying the individual resource would be much more useful than failing the entire stack deployment, particularly as a manual redeployment of the whole stack may hit the same issue again midway through.

## Expected behavior

Retry the throttled call, probably after a short delay

## Helpful Links to speed up research and evaluation

* [Discussion in the AWS forum](https://forums.aws.amazon.com/thread.jspa?threadID=240384)
* two related bugs in Serverless Framework, along with some workarounds if you're using that: \[[1](https://github.com/serverless/serverless/issues/3339)\] \[[2](https://github.com/serverless/serverless/issues/5142)\]. These workarounds boil down to either looping over retrying the whole stack, or making each function depend on one another in a series so that only one deploys at a time.

## Category (required)

Compute, Management

The issue names AWS::Lambda::Function but no repository files, tests, or entry points, so first locate the resource implementation and its deployment retry handling. Review the linked AWS forum and Serverless Framework issues for context; done means throttled calls retry after a short delay instead of failing the entire stack deployment.

Written by the indexing model from the issue text.