Use dynamic struct validation for entities card rows

[spacegaier]

Breaking change

Proposed change

Currently in the entities card editor, we show a lot of false-positive warnings and errors which really confuses the users.

The reason is that as all the existing row configs were in a union and the validation logic checked them all and basically listed all combinations of potential issues. Now by using dynamic from superstruct we only check the config that matches the type of the row.

=> We now only show relevant errors to the user.

Before:

There are two errors here: The mandatory attribute key is missing plus the not yet supported icon key is there. But as the YAML input is not matching any row config, we see a huge list of false-positive errors.

After:

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (thank you!)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Example configuration

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion: Entities card support for attributes broken for editing #9586
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• There is no commented out code in this PR.
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io