New Pattern: lambda-rekognition

Based on which feature and service of Rekognition you plan to use, Rek requires permission policy setup so that lambda functions can access them. Some of the API endpoints in Rek also require an S3 bucket to be setup for input and ouput. Rek's best practices recommend not to use the default buckets provided by Rek but to build your S3 buckets. These buckets need a policy too so that Rek can access the assets stored in those buckets for analysis

### Use Case

In my use case I use Rek to analyze images and may be videos too in the future. The solution creates a new bucket and enables policies that allow Rek to access the contents of the bucket for images. This bucket is isolated from the other data buckets since we only want Rek to be able to read the data that it requires (least privilege and only allow what is required)

### Proposed Solution

1. Provide the flexibility to the user to specify which Amazon Rek services does he plan to integrate with
2. Build the service role permissions required to access lambda
3. If the service selected requires S3 bucket, create the bucket too and update the bucket permissions as required by Rek to access it

### Other
I currently use this pattern in https://aws.amazon.com/solutions/implementations/discovering-hot-topics-using-machine-learning/

* [X] :wave: I may be able to implement this feature request
* [ ] :warning: This feature might incur a breaking change

---

This is a :rocket: Feature Request

No files, tests, or entry points are named. Start by reviewing the repository's existing AWS CDK patterns and the Rekognition, Lambda, and S3 requirements described here; done means a reusable pattern supports selected Rekognition services with least-privilege roles, and provisions or configures S3 when required.

Written by the indexing model from the issue text.