Reintroduce unique_id for Netatmo sensor

[heinemml]

Description:

Short:

This commit adds back the unique_id property for Netatmo sensors with a really unique value. Additionally it makes the differentiation of Module Types more intuitive.

Long:

In commit e51427b there was already an attempt to add a unique_id in the new Entity Registry style to the Netatmo sensor. This assumed, that the value of self.module_id was a value unique for each Netatmo Module. (actually it changed from using module_id which was unique to self.module_id which was not unique for the unique_id)

This assumption was wrong as PR #4724 introduced a self.module_id which differed from module_id
as it was defined like this:

module_id = self.netatmo_data.\
            station_data.moduleByName(module=module_name)['_id']
self.module_id = module_id[1]

So self.module_id was actually only the second char of the module_id (which is a MAC Address). This was used in the Battery Code to destinguish between the different types of modules. So it was actually more representing a module_type.

This led to a unique_id like 2-Temperature which was pretty obvious to be clashing with other modules.

What this PR now implements:

• Use the type field provided by the Netatmo API to distinguish between module types instead of taking an undocumented Byte from the Module address. This is used for the calculation of the Battery Status.
• Use the full MAC-Address + SensorType to generate the unique_id. So the unique_id now looks like XX:XX:XX:XX:XX:XX-Temperature

Example entry for configuration.yaml (if applicable):

netatmo:
  api_key: YOUR_CLIENT_ID
  secret_key: YOUR_CLIENT_SECRET
  username: YOUR_USERNAME
  password: YOUR_PASSWORD

sensor:
  - platform: netatmo
    station: STATION_NAME
    modules:
      module_name1:
        - temperature
      module_name2:
        - temperature
        - battery_vp

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.

[pvizeli]

Why you use this variable?

[heinemml]

It is needed in the update function to distinguish the module type to calculate the correct battery level.