AWS::EC2::VPNConnection VpnTunnelOptionsSpecification - All tunnel settings ( like Phase1 / Phase2 / ike etc) should be configurable through cf

## Instructions for CloudFormation Coverage New Issues Template
1. Title
AWS::EC2::VPNConnection VpnTunnelOptionsSpecification - Alle Tunnel Settings ( like Phase1 / Phase2 / ike etc) should be configurable through cf

2. Scope of request -> AWS::Service::ResourceType::TheResource-ExistingAttribute supports A and B today, but not new C feature.

AWS Resource supports only following attributes:

`
{
"PreSharedKey" : String,
"TunnelInsideCidr" : String
}
`
Would really like to have
`
{
"PreSharedKey" : String,
"TunnelInsideCidr" : String
"DPDTimeoutSeconds": Integer
"IKEVersions": String
"Phase1DHGroupNumbers": String
"Phase1EncryptionAlgorithms": String
"Phase1IntegrityAlgorithms": String
"Phase1LifetimeSeconds": Integer
"Phase2DHGroupNumbers: Integer
"Phase2EncryptionAlgorithms: String
"Phase2IntegrityAlgorithms: String
"Phase2LifetimeSeconds: Integer
"RekeyFuzzPercentage: String
"RekeyMarginTimeSeconds: Integer
"ReplayWindowSize: Integer
}
`
3. Expected behavior ->
Can Set Tunneloptions via CF

4. Test case recommendation (optional) ->
Cloud Formation Sets Code

5. Links to existing API doc (optional)

https://docs.aws.amazon.com/AWSEC2/latest/APIReference/API_ModifyVpnTunnelOptionsSpecification.html

6. Category tag (optional)

Cloud Formation

Start with the linked AWS ModifyVpnTunnelOptionsSpecification API documentation and the requested VpnTunnelOptionsSpecification attributes in this issue. Determine how CloudFormation should expose those settings, then verify that the listed tunnel options can be configured through CloudFormation and are covered by an appropriate test or validation.

Written by the indexing model from the issue text.