Raise if referenced entity does not support service

[balloob]

Breaking change

If an entity is explicitly referenced as a target for a service that the entity doesn't support, we now raise an error instead of silently ignoring it.

Proposed change

If an entity is explicitly referenced for a service but the entity does not contain the supported_feature, raise an error instead of silently ignoring it.

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)
• 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
• 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.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

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

[balloob]

Was able to fix all tests except for 1:

Template Alarm Control Panel will only add supported_features for features it has a script defined for. However it does allow calling unsupported methods: the entity will update it's state but also log an error (source / test).

I think that we should fix this behavior in template alarm control panel. Two options:

1. Always add the supported feature flags and do not log an error
2. Remove the test

I went for 2 because the supported feature was not there, causing it to already be skipped.

[elupus]

I very much like this change. I don't like the silent errors. Maybe a specialized exception should be used for the not supported case?

[frenck]

LGTM ✅

[thecode]

Looks good for webostv

[chemelli74]

Looks fine for SamsungTV