Allow name-only location updates for mobile_app device_tracker

[zacwest]

Proposed change

Allows sending name-only updates to the device_trackers, for example to do home vs. not_home without exposing accurate location values.

Motivation here originates in multi-server support in the iOS app. We want to limit location exposure to some not-their-primary-server instances like a parent's or friend's instance.

I'm somewhat intentionally (rather than requiring one of the location_name/gps keys) including the ability to redact the device_tracker (no gps/location name) and get it into the 'unknown' state.

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.

[probot-home-assistant]

Hey there @robbiet480, mind taking a look at this pull request as it has been labeled with an integration (mobile_app) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[dshokouhi]

We have also had this request in the android app where people dont want to report precise location but only zone names as well. One other thing we can do too with this change is to link wifi SSIDs to zones for users who do not have google services.

CC: @JBassett

[JBassett]

We have also had this request in the android app where people dont want to report precise location but only zone names as well. One other thing we can do too with this change is to link wifi SSIDs to zones for users who do not have google services.

CC: @JBassett

I think it best to just start with zone only before worrying about SSID -> location mapping.

[frenck]

Thanks, @zacwest 👍