New Pattern: aws-lambda-cr-apigateway

Add your +1 👍 to help us prioritize
---

## Overview:
This AWS Solutions Construct implements an Inline AWS Lambda function and custom resource to invoke an API endpoint and post user provided metrics data

## User provided props for the construct:
* URL for API endpoint
* Metrics data as `ResourceProperties` JSON blob
* Optional flag to append `UUID` as unique identifier for every request (default: true)
* Optional `lambda.Function` an existing instances of Lambda Function (default: None)
* Optional `lambda.FunctionProps` to deploy new Lambda Function (default: Default props are used)

## Default settings

Out of the box implementation of the Construct without any override will set the following defaults:

### AWS Lambda Function
* Configure least privilege access IAM role for Lambda function
* Enable reusing connections with Keep-Alive for NodeJs Lambda function

### AWS CloudFormation CustomResources
* Generate the unique identifier (UUID) per request
* Post the user provided `ResourceProperties` (metrics data) + UUID to the API endpoint

Start by reviewing existing AWS Solutions Constructs patterns and the AWS Lambda and CloudFormation CustomResources interfaces. Define the construct around the listed endpoint, ResourceProperties JSON, UUID, and Lambda configuration options, then verify that it applies least-privilege access, reuses Node.js connections, and posts the metrics data with the UUID.

Written by the indexing model from the issue text.