feat: Werks-Token im Einrichtungsdialog vorbelegen

Die Firmware antwortet im Auslieferungszustand und nach jedem Werksreset mit
dem oeffentlichen Werks-Token aabbccddeeff0011223344 - genau wie ninlight.
Wie ha-ninlight belegt die Integration es deshalb im Dialog vor, beim
manuellen Einrichten, beim Fund per mDNS und in den Texten zur
Token-Erneuerung.

custom_components/ninstrip/translations/en.json

@@ -3,7 +3,7 @@
     "step": {
       "user": {
         "title": "Add ninstrip",
-        "description": "Host and API token of the device. The token is printed once on the serial console at first boot; a factory reset creates a new one.",
+        "description": "Host and API token of the device. A factory-new or factory-reset device uses the default token, which is prefilled. If you set your own, enter it here.",
         "data": {
           "host": "Host",
           "token": "API token"
@@ -18,7 +18,7 @@
       },
       "reauth_confirm": {
         "title": "Renew token",
-        "description": "The device at {host} rejects the stored token. After a factory reset it has a new one.",
+        "description": "The device at {host} rejects the stored token. After a factory reset the default token applies again.",
         "data": {
           "token": "API token"
         }