save null module outputs in state

[jbardin]

Although they are not serialized to the final stored state, all module outputs must be saved in the state for evaluation. There is no defined schema which is used to identify the overall type of module outputs, so all outputs must exist in the state to build the correct type for proper evaluation.

A corresponding change will be backported to v1.3 manually, since this commit overlaps with conflicting changes in main.

[github-actions]

Reminder for the merging maintainer: if this is a user-visible change, please update the changelog on the appropriate release branch.

[ronmjf]

Hi, is that fix lead to the following behavior changes?
in 1.2.9 when we apply and then destroy without having resources a new state will create, in the new version in such case there is no new state creation.

[alisdair]

Hi @ronmjf. I can't follow what you're asking here. Could you please file a bug report with a detailed reproduction so that we can investigate further?

[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 contributions.
If you have 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.