fix (regression): compose build render build output with tty support

[ndeloof]

What I did
buildkit (actually, containerd/console) requires a *File to access the raw terminal and render build progress UI
it actually can't just be based on a file descriptor (we can get for dockerCli.Out().FD()) as windows support requires an actual file 🥲
so .. we have to assume dockerCli.Out == os.Stdout, which basically makes dockerCli.Out abstraction useless 🥹

Related issue
fixes #13099

(not mandatory) A picture of a cute animal, if possible in relation to what you did

[thaJeztah]

Hm... interesting; I saw this PR and recalled I stumbled on something similar. While it's for In() in this case, I guess this may partially answer the question I dropped in a TODO here, but I had no Windows machine to verify those bits; https://github.com/docker/cli/blob/a1035b0796241b3bbd0f41940525373001fc146c/cli/command/registry.go#L128-L139

func PromptUserForCredentials(ctx context.Context, cli Cli, argUser, argPassword, defaultUsername, serverAddress string) (registrytypes.AuthConfig, error) {
	// On Windows, force the use of the regular OS stdin stream.
	//
	// See:
	// - https://github.com/moby/moby/issues/14336
	// - https://github.com/moby/moby/issues/14210
	// - https://github.com/moby/moby/pull/17738
	//
	// TODO(thaJeztah): we need to confirm if this special handling is still needed, as we may not be doing this in other places.
	if runtime.GOOS == "windows" {
		cli.SetIn(streams.NewIn(os.Stdin))
	}

Similar code in another place; https://github.com/docker/cli/blob/a1035b0796241b3bbd0f41940525373001fc146c/internal/prompt/prompt.go#L90-L93

Definitely looks like something to look into. The Streams types are convenient, but it's definitely possible that either someone implemented them with the wrong assumptions, or that these subtleties got lost during some refactor.