aws-codepipeline-actions: New action to deploy code to an existing Lambda Function

### Describe the feature

A LambdaCodeDeploymentAction. A new action for a deploy stage of CodePipelines that allows either a .zip file from an S3 bucket or an Artifact from CodeBuild to be deployed to a Lambda function.

### Use Case

Its frustrating that my Lambda logic and my CDK have to be in the same repository so that when I update my Lambda it updates the code deployed to the Lambda function. The Infrastructure and the code that runs on the infrastructure should be separate. By doing this, I can use a source action to gather my lambda code from a separate repository to my CDK, build the code to create a .ZIP and then deploy that code to Lambda. All without having to update the CDK repository.

### Proposed Solution

As described above, creating a LambdaCodeDeploymentAction Action to fulfil this deployment. A feature that is available through the console using the 'Upload from' button.

### Other Information

_No response_

### Acknowledgements

- [ ] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### CDK version used

2.35.0

### Environment details (OS name and version, etc.)

Mac OS Monterey 12.5.1

Start in the aws-codepipeline-actions package and compare its existing CodePipeline action implementations with the Lambda console's “Upload from” behavior. Confirm support for an S3 .zip and a CodeBuild artifact targeting an existing Lambda function, then add coverage for both paths.

Written by the indexing model from the issue text.