Use CONF_RECIPIENT for default recipient in config

[rohankapoorcom]

Description:

Use the new deprecated vol validator to replace ATTR_TARGET with CONF_RECIPIENT in tpklink_lte.

Breaking Change: target has been deprecated and replaced with recipient in the tplink_lte configuration. This is a soft deprecation in this release and will automatically become a hard breaking change in Home Assistant version 0.91.0.

Related issue (if applicable): fixes #20671

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

Example entry for configuration.yaml (if applicable):

tplink_lte:
  - host: IP_ADDRESS
    password: SECRET
    notify:
      - name: sms1
        recipient: "+15105550123"
      - name: sms2
        recipient: "+55520525252"

Checklist:

• The code change is tested and works locally.
• Local tests pass with tox. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.

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

• Documentation added/updated in home-assistant.io

[MartinHjelmare]

When should we announce the breaking change? Now here, or later when we hit invalidation?

[rohankapoorcom]

It feels like we need a new section of the release notes for future breaking changes. Because we should announce now that this migration is necessary and will be required when we hit invalidation.

[dgomes]

if a user can postpone, he will postpone... by all means, a breaking change must be announced ASAP, and not wait for the final version.

We are just being nice not actually breaking stuff :)

[rohankapoorcom]

I think we need it mentioned in every set of release notes between now and invalidation or at the very least once now and once at invalidation.

[rohankapoorcom]

Tagged as breaking change and breaking change note added.