Backport of list: send non-null "config" object to provider when not present in the list block into v1.14

[github-actions]

Backport

The automatic backport failed, so I have manually cherry-picked the changes in this.

This PR is auto-generated from #37620 to be assessed for backporting due to the inclusion of the label 1.14-backport.

🚨

Warning automatic cherry-pick of commits failed. If the first commit failed,
you will see a blank no-op commit below. If at least one commit succeeded, you
will see the cherry-picked commits up to, not including, the commit where
the merge conflict occurred.

The person who merged in the original PR is:
@dsa0x
This person should resolve the merge-conflict(s) by either:

• Manually completing the cherry picks into this branch
• Creating a new branch and manually cherry-picking all commits being backported

merge conflict error: POST https://api.github.com/repos/hashicorp/terraform/merges: 409 Merge conflict []

The below text is copied from the body of the original PR.

---

This PR ensures that when a list config isn't given a config block, terraform sends a non-null config to the provider RPC. Also, we want to validate the existence of the config block if any of its direct attribute or block is required.

Because we were already manually constructing a schema for the list block anyway, I updated that schema to make config required if its direct attribute are required.

Target Release

1.14.x

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.

CHANGELOG entry

• This change is user-facing and I added a changelog entry.
• This change is not user-facing.

---

Overview of commits

• ffc40fa

• 2247707

• d672054

• 6119dab

• 8724d55

• 53fd330

• fdc63c7

• 0896cf7

• 2276835

• 7c5bf23

[github-actions]

Changelog Warning

Currently this PR would target a v1.14 release. Please add a changelog entry for in the .changes/v1.14 folder, or discuss which release you'd like to target with your reviewer. If you believe this change does not need a changelog entry, please add the 'no-changelog-needed' label.