feat: Add CodeDeploy Lifecycle Hook event definition

[mw-root]

Issue number: #5171

Summary

This is a simple change to implement the lambda event type CodeDeployLifeCycleHookLambdaEvent.

This event only provides DeploymentId and LifecycleEventHookExecutionId (at least in my experience)

Changes

This adds a new DictWrapper inherited class to define the properties passed by CodeDeployment.

User experience

This allows users to use the new class as an event type in their lambda handler

from aws_lambda_powertools.utilities.data_classes import (
  event_source,
  CodeDeployLifeCycleHookLambdaEvent,
)

def lambda_handler(
    event: CodeDeployLifeCycleHookLambdaEvent, context: LambdaContext
) -> None:
  ...

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

This is new functionality and is not a breaking change.

Acknowledgment

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[boring-cyborg]

Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need.
In the meantime, check out the #python channel on our Powertools for AWS Lambda Discord: Invite link

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[dreamorosi]

Thank you for taking the time to open this PR!

As discussed in the linked issue, we'll revisit this once v3 has been released.

[leandrodamascena]

Hi @mw-root! Thank you very much for submitting this PR! We made some changes to our branches because we had to release V3 and this PR became impossible to merge due to too many conflicts.

Do you mind closing this PR and opening another one against develop? You may need to pull the repository/branches again because we changed a lot.

[mw-root]

@leandrodamascena sounds good, #5219 has been created for this.