Correct nil MaxItemsOne handling in the bridge

[VenelinMartinov]

What happened?

The root cause pulumi/pulumi-aws#3427 seems to be that in Create and Update we pass nil for unspecified MaxItemsOne properties while in most cases TF passes an empty collection. See pulumi/pulumi-aws#3427 (comment) for details.

We tried to address in #1725 but hit #1762 which causes a panic in Azure, so a blocker for further progress here.

We should address this.

A painful point here was that iteration was extremely painful. We have practically no tests around this in the bridge and downstream tests revealed multiple issues and subtleties. We might want to start with some pulumi->TF cross tests like in #1728.

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).

[VenelinMartinov]

Blocked by #1762