Pass PlanResourceChange through downstream tests

[VenelinMartinov]

What happened?

@t0yv0 recently suggested running PlanResourceChange through downstream tests as a short-term way to gain more confidence in it.

This should help with #1785

We already know about some issues (GCP bucket) but it might be useful to learn about other problematic resources

Example

.

Output of pulumi about

.

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

[t0yv0]

This would be much appreciated since any bugs discovered here also probably affect AWS users through a handful of enrolled resources, and would also be happy-path simple bugs, not corner-case bugs discovered by randomized testing.

[VenelinMartinov]

I ran a round of downstream tests but we'd get more valuable results after #1849, so I'll finish that up first.

[VenelinMartinov]

Ok, biggest ones from the first run:

A bunch of panics: #1964 and #1966 maybe all root caused by #1916 and #1915

2 tfgen issues: #1965

A bunch of unexpected updates: #1967