Add nerdctl compose stop command

[djdongjin]

Fix #666

This implementation uses nerdctl stop [flags] container to stop all containers in given services, similar to how compose down works link.

I didn't use a WaitGroup to parallelize the nerdctl stop calls, as in here, since I'm not sure what forcibly/gracefully means. Thanks for any explanation and I can optimize (seems some refactor/dedup can be done here as well)

Also in the same place, it seems like a bug. This line should be outside of for loop right?

I'll also try to add test as well.

$ cat full.yaml
version: '3.1'

services:
  service1:
    image: alpine:3.13
    command: "sleep infinity"
  service2:
    image: alpine:3.13
    command: "sleep infinity"

$ sudoe nerdctl compose -f full.yaml up -d
INFO[0000] Ensuring image alpine:3.13
...
$ sudoe nerdctl ps
CONTAINER ID    IMAGE                            COMMAND             CREATED           STATUS    PORTS    NAMES
6ab9f4de1c07    docker.io/library/alpine:3.13    "sleep infinity"    17 seconds ago    Up                 orphan_service2_1
e046dbf0bdf3    docker.io/library/alpine:3.13    "sleep infinity"    17 seconds ago    Up                 orphan_service1_1
$ sudoe nerdctl compose -f full.yaml stop service1
INFO[0000] Stopping container orphan_service1_1
$ sudoe nerdctl ps -a
CONTAINER ID    IMAGE                              COMMAND             CREATED               STATUS                         PORTS    NAMES
...
6ab9f4de1c07    docker.io/library/alpine:3.13      "sleep infinity"    About a minute ago    Up                                      orphan_service2_1
e046dbf0bdf3    docker.io/library/alpine:3.13      "sleep infinity"    About a minute ago    Exited (137) 13 seconds ago             orphan_service1_1
...

Signed-off-by: Jin Dong jindon@amazon.com

[djdongjin]

Seems the CI failed due to a flaky test (#767). The issue is due to conflict container names.

nerdctl/cmd/nerdctl/run_mount_linux_test.go

Lines 232 to 237 in e83e18b

	runContainer()
	base.EnsureContainerStarted(containerName)
	base.Cmd("exec", containerName, "cat", "/mnt/file").AssertOutExactly("rev0")
	base.Cmd("exec", containerName, "sh", "-euc", "echo -n \"rev1\" >/mnt/file").AssertOK()
	base.Cmd("rm", "-f", containerName).AssertOK()
	runContainer()

# log
=== CONT  TestRunCopyingUpInitialContentsShouldNotResetTheCopiedContents
    testutil.go:458: buildkitHost="unix:///run/user/1000/buildkit-nerdctl-test/buildkitd.sock"
    run_mount_linux_test.go:233: container nerdctl-testruncopyingupinitialcontentsshouldnotresetthecopiedcontents is now running
    run_mount_linux_test.go:230: assertion failed: res.ExitCode is not exitCode: time="2022-11-10T00:45:37Z" level=fatal msg="name \"nerdctl-testruncopyingupinitialcontentsshouldnotresetthecopiedcontents\" is already used by ID \"7ce7a2031325302a265d2ed8836b5179488fd6835d6938325b52ec18e7e5e7d9\""
        
--- FAIL: TestRunCopyingUpInitialContentsShouldNotResetTheCopiedContents (2.24s)

Within the same file, another test case seems avoid the issue by not specifying containerName in the 2nd run:

nerdctl/cmd/nerdctl/run_mount_linux_test.go

Line 56 in e83e18b

"--name", containerName,

v.s.

nerdctl/cmd/nerdctl/run_mount_linux_test.go

Line 70 in e83e18b

"--rm",

[AkihiroSuda]

Thanks

[AkihiroSuda]

thanks