Create models for the myriad of AWS Lambda event types

For feral-lambda to be useful for the "zoo" of Lambda types available on AWS, we need to provide models for the various events (aka "triggers") and responses used by each of these lambdas. These will live in the feral-lambda-events module.

We are currently sourcing them from the Java and JavaScript/TypeScript implementations.

The TypeScript definitions are especially important, because they are the definitive representation of these events as "plain old JavaScript objects" which is isomorphic to their JSON representation. Therefore, our models should match them exactly in name, structure, etc. in order for parsing to work correctly.

For an example of this, see the existing events:
https://github.com/typelevel/feral/blob/main/lambda/shared/src/main/scala/feral/lambda/events/

• ActiveMQEvent
• APIGatewayCustomAuthorizerEvent
• APIGatewayProxyRequestEvent https://github.com/typelevel/feral/pull/409
• APIGatewayProxyResponseEvent https://github.com/typelevel/feral/pull/409
• APIGatewayV2CustomAuthorizerEvent
• APIGatewayV2HTTPEvent
• APIGatewayV2HTTPResponse
• APIGatewayV2WebSocketEvent https://github.com/typelevel/feral/pull/476
• APIGatewayV2WebSocketResponse
• ApplicationLoadBalancerRequestEvent
• ApplicationLoadBalancerResponseEvent
• AppSyncLambdaAuthorizerEvent
• AppSyncLambdaAuthorizerResponse
• CloudFormationCustomResourceEvent
• CloudFrontEvent
• CloudWatchLogsEvent
• CodeCommitEvent
• CognitoEvent
• CognitoUserPoolCreateAuthChallengeEvent
• CognitoUserPoolCustomMessageEvent
• CognitoUserPoolDefineAuthChallengeEvent
• CognitoUserPoolEvent
• CognitoUserPoolMigrateUserEvent
• CognitoUserPoolPostAuthenticationEvent
• CognitoUserPoolPostConfirmationEvent
• CognitoUserPoolPreAuthenticationEvent
• CognitoUserPoolPreSignUpEvent
• CognitoUserPoolPreTokenGenerationEvent
• CognitoUserPoolVerifyAuthChallengeResponseEvent
• ConfigEvent
• ConnectEvent
• DynamodbEvent https://github.com/typelevel/feral/pull/68
• IoTButtonEvent
• KafkaEvent https://github.com/typelevel/feral/pull/552
• KinesisAnalyticsFirehoseInputPreprocessingEvent
• KinesisAnalyticsInputPreprocessingResponse
• KinesisAnalyticsOutputDeliveryEvent
• KinesisAnalyticsOutputDeliveryResponse
• KinesisAnalyticsStreamsInputPreprocessingEvent
• KinesisEvent https://github.com/typelevel/feral/pull/75
• KinesisFirehoseEvent
• LambdaDestinationEvent
• LexEvent
• RabbitMQEvent
• S3BatchEvent https://github.com/typelevel/feral/pull/231
• S3BatchResponse https://github.com/typelevel/feral/pull/231
• S3Event https://github.com/typelevel/feral/pull/354
• ScheduledEvent https://github.com/typelevel/feral/pull/521
• SecretsManagerRotationEvent
• SimpleIAMPolicyResponse
• SNSEvent https://github.com/typelevel/feral/pull/195
• SQSEvent https://github.com/typelevel/feral/pull/58
• any more?

Start in the existing event models under lambda/shared/src/main/scala/feral/lambda/events/ and compare the unchecked event types with the AWS Java and TypeScript definitions linked in the issue. Add models in the feral-lambda-events module that match the TypeScript names and JSON structure; done means the selected event types and responses are represented for parsing.