fix(ec2): vpcpeeringconnection fixed fields for resolvers, change tagger

[haarchri]

Signed-off-by: haarchri [email protected]

Description of your changes

• Changed code-generator config yaml to correctly exclude VpcId and PeerVpcId
• added VpcId and PeerVpcId to preCreate
• removed old implementation for TagSpecification
• added generic tagger, as tagger we use in other ec2 resources

Fixes #1033
Replace for #1034

I have:

• Read and followed Crossplane's contribution process.
• Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

NAME                                                 READY   SYNCED   EXTERNAL-NAME
vpcpeeringconnection.ec2.aws.crossplane.io/example   True    True     pcx-033c398f6652f347c

[linuxbsdfreak]

@haarchri When will this be mergred ? I have a composition that i need it for testing.

[chlunde]

@haarchri looks good to me, some conflicts needs to be resolved