Add `VPCPeeringConnection` support to ec2-controller

[a-hilaly]

The current state of the ec2-controller lacks support for managing VPC Peering Connections. This feature request aims to enhance the capabilities of the ec2-controller by adding comprehensive support for creating, updating, deleting, and accepting VPC Peering Connections.
API definitions:

• https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_CreateVpcPeeringConnection.html
• https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_DeleteVpcPeeringConnection.html
• https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_AcceptVpcPeeringConnection.html
• https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ModifyVpcPeeringConnectionOptions.html

[marcdavoli]

/assign

[marcdavoli]

A bit of additional context:

This PR adds the VpcPeeringConnection custom resource and covers the standard API lifecycle CRUD operations.

• feat(VPCPeeringConnection): add support for custom resource and additional fields for Modify OP and auto-accepting ec2-controller#158

This PR adds an enhancement to the VPC custom resource to allow it to Accept or Reject VPC Peering Connection coming from allow-listed or block-listed VPC IDs.

• WIP: feat(vpc): add auto acceptance & rejection of VPC Peering Connection requests ec2-controller#159

[marcdavoli]

I'll try to be at the meeting tomorrow to discuss this PR:
aws-controllers-k8s/ec2-controller#159

But given the original purpose of this Issue, I think we can close it.