…roconf#709)

…onf#710)

Closes python-zeroconf#703

…thon-zeroconf#726)

- It was too easy to get confused about what was threadsafe and
  what was not threadsafe which lead to unexpected failures.
  Rename functions to make it clear what will be run in the event
  loop and what is expected to be threadsafe

- There is currently a bug in the implementation where an entry
  can exist in two places in the cache with different TTLs. Since
  a known answer cannot be both expired and expired at the same
  time, this is a bug that needs to be fixed.

- There should only be one unique record in the cache at
  a time as having multiple unique records will different
  TTLs in the cache can result in unexpected behavior since
  some functions returned all matching records and some
  fetched from the right side of the list to return the
  newest record. Intead we now store the records in a dict
  to ensure that the newest record always replaces the same
  unique record and we never have a source of truth problem
  determining the TTL of a record from the cache.

…roconf#724)

…ython-zeroconf#734)

…nf#736)

…thon-zeroconf#740)

…f#744)

…hon-zeroconf#745)

…-zeroconf#981)

…thon-zeroconf#988)

…on-zeroconf#998)

- Breakout functions without self-use

…oconf#1003)