cli-plugins: add build-time system plugin directory

[HeroCC]

Summary

Adds an optional system CLI plugin directory that downstream builds can set with the Go linker -X flag. This lets downstream packagers expose package-managed CLI plugins without requiring users to modify their Docker configuration.

If accepted, I plan on using this in homebrew's docker formula to avoid needing caveats (like this) for plugins.

Testing

• go test github.com/docker/cli/cli-plugins/manager
• go test -ldflags='-X github.com/docker/cli/cli-plugins/manager.additionalSystemPluginDir=/test/cli-plugins' github.com/docker/cli/cli-plugins/manager
• Built and installed a downstream package with the linker setting and confirmed its packaged Compose plugin is discovered.

$ docker info
Client: Docker Engine - Community
 Version:    HEAD-9eaf761
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.37.1
    Path:     /opt/homebrew/lib/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  5.5.1
    Path:     /opt/homebrew/lib/docker/cli-plugins/docker-compose

Release notes (optional)

Add support for configuring an additional system CLI plugin directory at build time.

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

Rex :)

[vvoland]

Looks good to me!

@thaJeztah WDYT?

[vvoland]

One nit though - could you please squash these commits into 1?

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[HeroCC]

@vvoland Done! Rebased into one commit. I also fixed the lint in the test.

[thaJeztah]

I want to have a closer look; my concern is that some of this code may also be used in (eg) docker compose; which may mean that compose now gets a different view of the world than the CLI itself, so resolve to a different plugin; even if the same config-file is used.