Cross tests for check: Investigate the need for applying TF defaults in Check

[VenelinMartinov]

What happened?

During the work on #1546, a possible discrepancy was found between how TF and the bridge handle TF-level defaults before Check.

The immediate issue was addressed there but there might be further redundancies we might be able to simplify.
Most of the TF methods don't require the TF defaults to be applied when creating the inputs.

Related to this is dealing with ConflictsWith and ExactlyOneOf in schema.go - we might be able to remove that logic if we were not applying the TF defaults.

More details: #1546 (comment)

This work will be much easier if we have a sensible framework for comparing TF to bridge behaviour.

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