3081 implement stopoptions for container restart

[s4ke]

closes #3081

- What I did

Upgrade moby/moby dependencies and try to fix compiler issues around StopOptions

- How I did it

go get
go mod vendor
Use the most straighforward fixes on each compiler issue

- How to test it

- Description for the changelog

Upgrade moby/moby dependencies to fix compiler issues around StopOptions

[s4ke]

This is currently failing on TestAllocateWithInvalidSubnet as discussed in #3081 on my machine. Could this be a bug in libnetwork?

/cc @dperny

[s4ke]

@thaJeztah PTAL if convenient, I think you are the right person to weigh in here, since the StopOptions commit was authored by you :)

[s4ke]

Seems like TestAllocateWithInvalidSubnet fails due to this change in libnetworkd in insertBitMask of vendor/github.com/docker/docker/libnetwork/ipam/allocator.go

[s4ke]

Yes, this was caused by the change in libnetworkd. this used to fail in line 574 of vendor/github.com/docker/docker/libnetwork/ipam/allocator.go, now it doesn't:

[s4ke]

seems to be caused by this commit moby/moby@3a938df

I will do a PR to moby/moby to handle the case of 1.1.1.1/32 which was left out in the PR.

[thaJeztah]

We should probably pick a commit (head) from the 22.06 branch in moby/moby, as master is currently used to work on the release after.

[s4ke]

in any case, the PR in moby/moby I linked is blocking this as both have the same code path. Will update once merged.

[s4ke]

Update from the PR in moby/moby: 1.1.1.1/32 is a valid network. The test in swarmkit is actually faulty and should probably be removed / revisited why it existed.

[thaJeztah]

Thanks @s4ke ! I had this branch locally and updated it to v23.0.0-beta.1, and also included the fix for the failing test (as discussed on the moby ticket); carrying this in #3103 (I kept your commit as starting point).

[s4ke]

so we can close this PR?

[thaJeztah]

Yup! I marked the other one to close this one automatically; it's been merged 👍

Thanks again!