test(ci): Install and run docker-mac-net-connect when running e2e on macos

[sudiptob2]

This PR introduces scripts to automate the setup and cleanup of docker-mac-net-connect for local macOS development environments.

Features

• Prompt Mac users to install and start the service before running e2e tests.
• Automatically stop the service afterward. Users will be responsible for stopping the service if needed.
• Disable via DOCKER_MAC_NET_CONNECT=false.

Covered Logic

• Skips setup if the application is already installed and running.
• Supports proxy via HOMEBREW_GOPROXY.

Fixes #6325

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 70.82%. Comparing base (d809446) to head (39631ee).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6368      +/-   ##
==========================================
+ Coverage   70.77%   70.82%   +0.04%     
==========================================
  Files         220      220              
  Lines       37132    37132              
==========================================
+ Hits        26280    26298      +18     
+ Misses       9308     9292      -16     
+ Partials     1544     1542       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[sudiptob2]

brew services info docker-mac-net-connect --json provides following output while my testing.

[
  {
    "name": "docker-mac-net-connect",
    "service_name": "homebrew.mxcl.docker-mac-net-connect",
    "running": false,
    "loaded": false,
    "schedulable": false,
    "pid": null,
    "exit_code": null,
    "user": "root",
    "status": "none",
    "file": "/Users/sudiptobaral/Library/LaunchAgents/homebrew.mxcl.docker-mac-net-connect.plist",
    "registered": true,
    "loaded_file": null,
    "command": "/opt/homebrew/opt/docker-mac-net-connect/bin/docker-mac-net-connect",
    "working_dir": null,
    "root_dir": null,
    "log_path": "/opt/homebrew/var/log/docker-mac-net-connect/std_out.log",
    "error_log_path": "/opt/homebrew/var/log/docker-mac-net-connect/std_error.log",
    "interval": null,
    "cron": null
  }
]

During testing, I noticed that "running": false was returned even when docker-mac-net-connect was clearly running. The only reliable indicator I found was the user field:

• If the service is stopped, the user field is null.
• If the service is running, the user field is always populated (e.g., "root").