feat: add blkio device options to docker container update

[acouvreur]

• depends on vendor: github.com/moby/moby/api v1.55.0-rc.1, moby/client v0.5.0-rc.1 #7051

Closes#3325

Related to moby/moby#52651

- What I did

Add 5 options to docker container update to control the device blkio throttle.

- How I did it

I simply added the same options from the create command to the update command to be able to pass the blkio device arguments for the update.

- How to verify it

The current version of the moby/moby library does not forward those arguments even though they exist in the struct.

You need to set the moby/moby version to the one in moby/moby#52651 and then create a docker container with a certain blkio device throttle configuration and then update it using docker container update. Then you can inspect the container for those new values.

- Human readable description for the release notes

docker container update can now update the blkio device weights/IOPs

- A picture of a cute animal (not mandatory but encouraged)

[codecov-commenter]

Codecov Report

❌ Patch coverage is 0% with 30 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
cli/command/container/update.go	0.00%	30 Missing ⚠️

📢 Thoughts on this report? Let us know!

[vvoland]

Thinking if we could align with the compose format a little bit more: https://docs.docker.com/reference/compose-file/services/#blkio_config

[thaJeztah]

Had to do this otherwise it would not validate and send [nil] as slice, but it looks like it currently defaults to sending an empty slice, which would probably reset the existing values by default (so something to fix)

[thaJeztah]

Yeah, we probably should look; currently it's aligning with docker run / docker create, but agreed that these flags aren't ideal.

[thaJeztah]

Discussing with @vvoland on slack; given that there's still some bits to discuss (and a potential bug to be fixed); let's have a closer look at options and not rush.

If we have a good plan soon, it can still be in v29.6.0-rc.2, otherwise we could shift it to v29.7 (which should not be far in the future)