core: avoid diff mismatch on NewRemoved fields during -/+
core: avoid diff mismatch on NewRemoved fields during -/+

fixes #1508

In a DESTROY/CREATE scenario, the plan diff will be run against the
state of the old instance, while the apply diff will be run against an
empty state (because the state is cleared when the destroy node does its
thing.)

For complex attributes, this can result in keys that seem to disappear
between the two diffs, when in reality everything is working just fine.

Same() needs to take into account this scenario by analyzing NewRemoved
and treating as "Same" a diff that does indeed have that key removed.

rosbo/terraform-provider-google,rosbo/terraform-provider-google,hashicorp/terraform-provider-google,drebes/terraform-provider-google,selmanj/terraform-provider-google,ubschmidt2/terraform-provider-google,rosbo/terraform-provider-google,selmanj/terraform-provider-google,ubschmidt2/terraform-provider-google,nickithewatt/terraform-provider-google,drebes/terraform-provider-google,hashicorp/terraform-provider-google,ubschmidt2/terraform-provider-google,hashicorp/terraform-provider-google-beta,hashicorp/terraform-provider-google-beta,hashicorp/terraform-provider-google,terraform-providers/terraform-provider-google,hashicorp/terraform-provider-google-beta,ubschmidt2/terraform-provider-google,rosbo/terraform-provider-google,terraform-providers/terraform-provider-google,terraform-providers/terraform-provider-google,drebes/terraform-provider-google,terraform-providers/terraform-provider-google,nickithewatt/terraform-provider-google,hashicorp/terraform-provider-google,drebes/terraform-provider-google,selmanj/terraform-provider-google,terraform-providers/terraform-provider-google,hashicorp/terraform-provider-google-beta,nickithewatt/terraform-provider-google