[EPIC] Cross-testing coverage for Update

[iwahbe]

Pursuant to #2773, we are introducing integration level cross-tests (SDKv2, PF) for bridged provider operations. These allow us to easily verify that the behavior of bridged TF providers with Pulumi match the behavior of native terraform providers with Terraform. crosstests are written on a verb by verb basis. This EPIC describes the tests we need for the crosstest.Update verb.

As a pre-requisite to implementing any of these tests, we need:

• TODO: [SDKv2] Implement crosstest.Update
• TODO: [PF] Implement crosstest.Update

Some of these tests need:

• Cross-test unknown values #1858
• Assert on outputs of crosstest.Update (SDKv2) (similar to Assert on outputs in SDKv2 Cross-tests [Create][SDKv2] #2523)
• Assert on outputs of crosstest.Update (PF) (similar to Assert on outputs in SDKv2 Cross-tests [Create][PF] #2524)

We won't attempt to be as through with testing inputs as we were for #2537, since we presume that inputs and outputs will flow appropriately.

Issues:

• Verify default values:
  • Going from an empty value to a non-empty value
  • Going from a non-empty value to an empty value
  • Verify changing a value works as expected
  • Verify changing a nested value {List,Set,Map}[T] works as expected
  • Verify that changing a {List,Set,Map} from non-empty to empty and vice versa works as expected
  • Verify that adding or removing an element from a {List,Set,Map} (without hitting empty) works as expected
  • Verify that List re-orders work as expected
  • Verify that Set re-orders work as expected
  • Verify that a no-op update works as expected
  • Verify that changes within an object work as expected

[VenelinMartinov]

I wonder if we can somehow re-use the tests for Diff here - the setup should be similar.