Bump zeroconf to 0.36.2 (#55459)

- Now sends NSEC records when requesting non-existent address types
  Implements RFC6762 sec 6.2 (http://datatracker.ietf.org/doc/html/rfc6762#section-6.2)

- This solves a case where a HomeKit bridge can take a while to update
  because it is waiting to see if an AAAA (IPv6) address is available

homeassistant/components/zeroconf/manifest.json

@@ -2,7 +2,7 @@
   "domain": "zeroconf",
   "name": "Zero-configuration networking (zeroconf)",
   "documentation": "https://www.home-assistant.io/integrations/zeroconf",
-  "requirements": ["zeroconf==0.36.1"],
+  "requirements": ["zeroconf==0.36.2"],
   "dependencies": ["network", "api"],
   "codeowners": ["@bdraco"],
   "quality_scale": "internal",

homeassistant/package_constraints.txt

@@ -34,7 +34,7 @@ sqlalchemy==1.4.23
 voluptuous-serialize==2.4.0
 voluptuous==0.12.1
 yarl==1.6.3
-zeroconf==0.36.1
+zeroconf==0.36.2
 
 pycryptodome>=3.6.6
 

requirements_all.txt

@@ -2453,7 +2453,7 @@ youtube_dl==2021.04.26
 zengge==0.2
 
 # homeassistant.components.zeroconf
-zeroconf==0.36.1
+zeroconf==0.36.2
 
 # homeassistant.components.zha
 zha-quirks==0.0.60

requirements_test_all.txt

@@ -1373,7 +1373,7 @@ yeelight==0.7.4
 youless-api==0.12
 
 # homeassistant.components.zeroconf
-zeroconf==0.36.1
+zeroconf==0.36.2
 
 # homeassistant.components.zha
 zha-quirks==0.0.60