Ensure we have valid config AFTER merging packages #13015

[kellerza]

Description:

My initial diagnosis for #13015 did not include empty components inside packages

This fixes it for #13015 and check_config which will currently suffer from the same fate

Example entry for configuration.yaml (if applicable):

homeassistant:
   packages:
      one:
         python_script:

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass

If the code does not interact with devices:

• Tests have been added to verify that the new code works.

[OttoWinter]

PEP8 recommends:

Also, beware of writing if x when you really mean if x is not None -- e.g. when testing whether a variable or argument that defaults to None was set to some other value. The other value might have a type (such as a container) that could be false in a boolean context!

for key, value in config.items():
    if value is None:
        config[key] = {}

[kellerza]

I think my version might be equal to: config[key] = value or {}, which is the correct behaviour

[kellerza]

Or let correct by saying current behaviour

[OttoWinter]

Ok, but then the comment should rather be:

# Ensure we have no None, empty or false values after merge
for key, value in config.items():
    if not value:
        config[key] = {}