Fixes a bug with TCP health check request generation where ResourcePath ...

...should not be included in the request XML

There is an error when you try to create a TCP health check in route53 due to the fact that the tcp health check does not support ResourcePath

Invalid request:

    <CallerReference>f239c81e-a761-49d6-b4f8-05d5ed8ec167</CallerReference>
    
        <HealthCheckConfig>
            <IPAddress>54.54.54.54</IPAddress>
            <Port>1024</Port>
            <Type>TCP</Type>
            <ResourcePath>None</ResourcePath>
            
            
            <RequestInterval>10</RequestInterval>
            <FailureThreshold>7</FailureThreshold>
        </HealthCheckConfig>
    
    </CreateHealthCheckRequest>

Error:

    <ErrorResponse xmlns="https://route53.amazonaws.com/doc/2013-04-01/">
        <Error><Type>Sender</Type><Code>InvalidInput</Code><Message>TCP health checks must not have a resource path specificed.</Message></Error><RequestId>4bf97687-c58c-11e3-9c4f-b18f7840909a</RequestId>
    </ErrorResponse>


Valid request with this patch:

    <CallerReference>f239c81e-a761-49d6-b4f8-05d5ed8ec167</CallerReference>
    
        <HealthCheckConfig>
            <IPAddress>54.54.54.54</IPAddress>
            <Port>1024</Port>
            <Type>TCP</Type>
            
            
            
            <RequestInterval>10</RequestInterval>
            <FailureThreshold>7</FailureThreshold>
        </HealthCheckConfig>
    
    </CreateHealthCheckRequest>