Ensure that Terraform configuration overrides any changes in target Twingate system

[alexmensch]

twingate_connector:

• If the connector does not exist, it must be recreated per the Terraform configuration.
• The name must be set to the configured name in the Terraform configuration. Name changes can be done via the connectorUpdate mutation.
• The connector must be attached to the same remote network as in the Terraform configuration. It's currently not possible in our product to move connectors between remote networks, so this scenario must trigger an error when running terraform apply.

twingate_remote_network:

• If the remote network does not exist, it must be recreated per the Terraform configuration.
• The name must be set to the configured name in the Terraform configuration. Name changes can be done via the remoteNetworkUpdate mutation.

twingate_resource:

• If the Twingate resource does not exist, it must be recreated per the Terraform configuration.
• If any attributes of the Twingate resource have been changed, they must be updated per the Terraform configuration. Changes can be done via the resourceUpdate mutation.

[vmanilo]

Added fix for twingate_connector for 3rd bullet-point https://github.com/Twingate/terraform-provider-twingate/pull/98

[vmanilo]

@alexmensch FYI didn't notice issues with other cases, do you how to reproduce issues?

[arthur-twingate]

https://twingate.atlassian.net/browse/SUP-172 Attempting to Link

[alexmensch]

@alexmensch FYI didn't notice issues with other cases, do you how to reproduce issues?

I actually don't have reproduction use cases -- these have been reported from customers, so if you're seeing those cases as working correctly, it sounds like we're okay?

[romankor]

@alexmensch looks like we ok here after merging PR #98 , i am closing this one