Add IPv6 zone test.

It looks like an arbitrary zone name works. If Docker daemon ever starts
validating it (against what?) we either have to try to fix this test by
a valid value, or remove it again.

tests/integration/targets/docker_container/tasks/tests/options.yml

@@ -2950,9 +2950,22 @@ avoid such warnings, please quote the value.' in log_options_2.warnings"
     published_ports:
     - '127.0.0.1:9002:9002/tcp'
     - '[::1]:9003:9003/tcp'
+    - '[fe80::1%test]:90:90/tcp'
     force_kill: yes
   register: published_ports_5
 
+- name: published_ports (ports with IP addresses, idempotent)
+  docker_container:
+    image: "{{ docker_test_image_alpine }}"
+    command: '/bin/sh -c "sleep 10m"'
+    name: "{{ cname }}"
+    state: started
+    published_ports:
+    - '127.0.0.1:9002:9002/tcp'
+    - '[::1]:9003:9003/tcp'
+    - '[fe80::1%test]:90:90/tcp'
+  register: published_ports_6
+
 - name: published_ports (no published ports)
   docker_container:
     image: "{{ docker_test_image_alpine }}"
@@ -2963,7 +2976,7 @@ avoid such warnings, please quote the value.' in log_options_2.warnings"
     comparisons:
       published_ports: strict
     force_kill: yes
-  register: published_ports_6
+  register: published_ports_7
 
 - name: cleanup
   docker_container:
@@ -2979,7 +2992,8 @@ avoid such warnings, please quote the value.' in log_options_2.warnings"
     - published_ports_3 is not changed
     - published_ports_4 is changed
     - published_ports_5 is changed
-    - published_ports_6 is changed
+    - published_ports_6 is not changed
+    - published_ports_7 is changed
 
 ####################################################################
 ## pull ############################################################