remove old warnings about changes from refresh

These logs were added to help diagnose issues with providers
transitioning to post-0.12 terraform. Now that all providers have been
using the new protocol for considerable time, we no longer see questions
about behavior that the logs help explain. Since legitimate external
updates also show up in these warnings, the logs are only extra noise
or at least redundant with the actual legacy SDK warnings.

internal/terraform/node_resource_abstract_instance.go

@@ -707,19 +707,6 @@ func (n *NodeAbstractResourceInstance) refresh(ctx EvalContext, deposedKey state
 	ret.Value = newState
 	ret.Private = resp.Private
 
-	// We have no way to exempt provider using the legacy SDK from this check,
-	// so we can only log inconsistencies with the updated state values.
-	// In most cases these are not errors anyway, and represent "drift" from
-	// external changes which will be handled by the subsequent plan.
-	if errs := objchange.AssertObjectCompatible(schema, priorVal, ret.Value); len(errs) > 0 {
-		var buf strings.Builder
-		fmt.Fprintf(&buf, "[WARN] Provider %q produced an unexpected new value for %s during refresh.", n.ResolvedProvider.Provider.String(), absAddr)
-		for _, err := range errs {
-			fmt.Fprintf(&buf, "\n      - %s", tfdiags.FormatError(err))
-		}
-		log.Print(buf.String())
-	}
-
 	// Call post-refresh hook
 	diags = diags.Append(ctx.Hook(func(h Hook) (HookAction, error) {
 		return h.PostRefresh(n.HookResourceIdentity(), deposedKey, priorVal, ret.Value)