[17.12] bump libnetwork to 0ef1f8c94fa85acacf88b9be75ae07de91d0b2a5

[thaJeztah]

Brings in a cherry pick of moby/libnetwork@76bfcb0

In sandbox creation we disable IPV6 config. But this causes problem in live-restore case
where all IPV6 configs are wiped out on running container. Hence extra check has been added
take care of this issue.

full diff:

moby/libnetwork@7dd202d...0ef1f8c

which includes these changes:

• [Backport 17.12] watchMiss fixes moby/libnetwork#2052 [Backport 17.12] watchMiss fixes
• [17.12] Enable IPV6 config on Sandbox creation on live-restore moby/libnetwork#2059 [17.12] Enable IPV6 config on Sandbox creation on live-restore

[thaJeztah]

@seemethere @jose-bigio could one of you restart CI?

[jose-bigio]

Failed with

20:29:56 ----------------------------------------------------------------------
20:29:56 FAIL: check_test.go:366: DockerSwarmSuite.TearDownTest
20:29:56 
20:29:56 check_test.go:371:
20:29:56     d.Stop(c)
20:29:56 daemon/daemon.go:395:
20:29:56     t.Fatalf("Error while stopping the daemon %s : %v", d.id, err)
20:29:56 ... Error: Error while stopping the daemon d9479c42896a3 : exit status 130
20:29:56 
20:29:56 
20:29:56 ----------------------------------------------------------------------
20:29:56 PANIC: docker_api_swarm_service_test.go:201: DockerSwarmSuite.TestAPISwarmServicesUpdateStartFirst
20:29:56 
20:29:56 [d9479c42896a3] waiting for daemon to start
20:29:56 [d9479c42896a3] daemon started
20:29:56 
20:29:56 [d9479c42896a3] daemon started
20:29:56 Attempt #2: daemon is still running with pid 31978
20:29:56 Attempt #3: daemon is still running with pid 31978
20:29:56 Attempt #4: daemon is still running with pid 31978
20:29:56 [d9479c42896a3] exiting daemon
20:29:56 ... Panic: Fixture has panicked (see related PANIC)
20:29:56 
20:29:56 ----------------------------------------------------------------------

Rerunning