Top-level attributes that conflict with Terraform meta arguments

[ewbankkit]

Terraform has a handful of meta-arguments such as provider that can conflict with top-level properties defined in CloudFormation schemas.
In fact the awscc_networkmanager_link resource has such a conflicting provider attribute.

1. Verify with Terraform Core that such a conflict exists
2. Determine how many resources are affected
3. Come up with a plan on how to handle these

Relates:

• Meta-Issue: Suppressed Resource Generation #156
• Framework allows top-level schema attributes that conflict with Terraform meta-arguments terraform-plugin-framework#136
• Terraform allows providers to define schema attributes that conflict with its meta-arguments terraform#29542

[ewbankkit]

awscc_networkmanager_link is the only resource that this applies to.
For now, suppress generation.

[ewbankkit]

In hashicorp/terraform-provider-aws#13251 the corresponding attribute is named provider_name.

[ewbankkit]

There are 4 resources with a top-level Provider property:

• awscc_codepipeline_custom_action_type
• awscc_datazone_environment
• awscc_datazone_subscription_target
• awscc_networkmanager_link

The aws_codepipeline_custom_action_type and aws_networkmanager_link resources name this attribute provider_name. There are not yet any corresponding DataZone resources in terraform-provider-aws.