Fix loading empty yaml files with include_dir_named

[pedrolamas]

Proposed change

This PR partially reverts the changes from #103912 as these have broken loading of packages with include_dir_named.

Type of change

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

Additional information

• This PR fixes or closes issue: fixes pxkages (or include_dir_named?) broken in 2024.1 #107166
• This PR is related to issue: Remove logic converting empty or falsy YAML to empty dict #103912
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• I have followed the perfect PR recommendations
• The code has been formatted using Ruff (ruff format homeassistant tests)
• 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

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[pedrolamas]

Apologies for the pushing my luck here, but this is quite a nasty bug (I am assuming this is a bug as the consequences of the original change impact a lot of users and as far as I can see, they were not documented), so I just wanted to see if I can get this prioritised for checking please?

[emontnemery]

Thanks @pedrolamas 👍

[emontnemery]

This PR allows empty yaml files when using !include_dir_named.
Should we also allow empty files when using !include_dir_list?

[pedrolamas]

Should we also allow empty files when using !include_dir_list?

My understanding (which might be wrong) is that only include_dir_named maps with the filename, all the others will ignore the filename and just consider the file content.