Add completion command and fix convert

[ulyssessouza]

What I did
Add completion command and fix convert

To test, you can trigger the completions with the following example:

1. Create a compose file with the following content:
   compose.yaml

services:
foo:
image: nginx
bar:
image: nginx
baz:
image: nginx

2. Then run the following command:

$ docker compose __complete up ""

This should print the 3 services as proposals

3. By running

$ docker compose __complete up "b"

This should propose the 2 services starting with the letter "b"

For now, the Docker CLI is not triggering compose's completion yet. That should be done in a following PR.

[milas]

LGTM! Can't wait to get it connected to the docker CLI 🎉

[milas]

Ah project name completion isn't working, it looks like the backend instance isn't initialized?

I'm getting not implemented error and all the funcs on the ServiceProxy are nil at the point that completeProjectNames is called 😭

[milas]

Oh, we lazily initialize the ServiceProxy via PersistentPreRunE which presumably does NOT run for the auto-completion 😬

compose/cmd/main.go

Lines 41 to 44 in db88241

	iferr:=plugin.PersistentPreRunE(cmd, args); err!=nil {
	returnerr
	}
	lazyInit.WithService(compose.NewComposeService(dockerCli))

[ulyssessouza]

@milas Good catch!
I changed to populate the serviceProxy on creation... We could actually get rid of this, but that can be useful on state tracing with interceptors.

[milas]

Nice! Project name completion looks good now. Can't wait 🥳

[nicksieger]

Should this close #8550 as well?