Handle integrations with empty services or failing to load during service description enumeration

[bdraco]

Proposed change

fixes #95581

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 #
• This PR is related to issue:
• 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 Black (black --fast 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.

[bdraco]

Needs more manual testing on production

[bdraco]

shell_command is a weird case here

shell_command % cat services.yaml

Empty file, shell_command services are dynamically created

Allowing it to be null is a problem because it breaks the frontend

      "shell_command": {
            "restart_pow": null,
            "call_remote": null
        },

ha-service-picker.ts:74 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'name')
    at ha-service-picker.ts:74:43
    at Array.forEach (<anonymous>)
    at F.<anonymous> (ha-service-picker.ts:67:10)
    at F.o [as _services] (memoize-one.esm.js:37:35)
    at F.<anonymous> (ha-service-picker.ts:93:38)
    at F.o [as _filteredServices] (memoize-one.esm.js:37:35)
    at F.value (ha-service-picker.ts:35:31)
    at F.update (lit-element.ts:160:24)
    at F.performUpdate (reactive-element.ts:1331:14)
    at F.scheduleUpdate (reactive-element.ts:1263:17)

[elupus]

I wonder if this only partly fixed the issue: danieldotnl/ha-multiscrape#215 they seem too have a partial services.yaml.