Don't use LOGGER.error for debug logging during scene entities check

[Sirs0ri]

Description

Change a LOGGER.error statement that's not used to log an error to a more approproate debug statement.

Motivation and Context

I new errors in my HA log after installing spook, and after I'd fixed all the repairs. Since the error's title was just Scene: scene.one_of_my_scenes, repeated multiple times for each scene, I checked the code and noticed that every time a scene's entities are scanned for missing entities (e.g. when saving a scene), the scene's id is logged as error. This PR changes the message's log level to debug.

How has this been tested?

1. changed the file locally
2. deleted the corresponding pycache file
3. restarted HomeAssistant
4. changed a scene, to see if the log's gone
5. error is no longer logged!
6. reverted the change locally, then repeated 2.-4. to check that the error comes back, which it does

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other

Checklist

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[frenck]

Thanks, @Sirs0ri 👍

../Frenck