Ignore attribute changes in automation trigger from/to

[amelchio]

Description:

This changes from/to filters on automation triggers to only consider actual state changes, not attribute updates. The change only makes a difference if just one of from/to is specified.

Using state as an alias of to is deprecated because it is ambiguous.

These changes were agreed upon in #7556.

Related issue (if applicable): fixes #6299 #7556

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.io#2665

Breaking change note 1: An automation state trigger that had only from or to (but not both) used to be triggered whenever state attributes changed, even if the actual from/to state remained the same. This has been changed so that from and to will only match when the state actually changes from or to the specified state.

Breaking change note 2: The automation state trigger used to allow state as an alias for to. This naming was a bit confusing and state has now been deprecated.

Example entry for configuration.yaml (if applicable):

This example no longer arms the alarm when GPS coordinates are updated while the device is home:

automation:
  - alias: ‘Arm alarm when leaving home'
    trigger:
      - platform: state
        entity_id: device_tracker.amelchio
        from: ‘home’

Checklist:

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated in home-assistant.github.io

If the code does not interact with devices:

• Local tests with tox run successfully.
• Tests have been added to verify that the new code works.

[balloob]

I like it 👍

[amelchio]

I have added a test and updated the documentation. I am happy with this now but would appreciate a review from @armills.

(Note: it turned out that for without to is already forbidden.)

[emlove]

LGTM. Thanks for putting it together! I think this behavior will be a lot more intuitive.