fix(lib): Keep specified empty objects

[jsteinich]

Fixes #1182

This is an alternative to #1322 that doesn't alter the output json in other ways.
I initially thought this approach would have many other side effects, but early testing hasn't revealed any (other than other things that were broken).

[jsteinich]

This is fixing a regression from 0.7, so would be nice to get into 0.8.

Thinking about this some more, it does make sense why the check isn't needed. The entire object will simply be undefined / not present in cases where it hasn't been set, so having it be an empty object means that it needed to have be explicitly set in the 1st place and we should respect that when synthesizing.

[jsteinich]

Ran into some issues with how the OutputReference types were handled. I tried a couple solutions, but settled on only keeping and empty object for them when explicitly specified. I don't believe it's very common for an empty block to signify configuration, so needing to be intentional about it seems fine.

[jsteinich]

Apparently the updated generated providers were enough to run out of memory when building the providers integration test. Had to alter test setup slightly in order to give node a large heap size.

[jsteinich]

Since main had a different approach added to deal with test memory, I cleaned this up to use that and just have the relevant changes.

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days. This helps our maintainers find and focus on the active issues. If you've found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.