Check brew install paths for socket_vmnet

[spowelljr]

Before:
If no socket_vmnet flags were provided minikube would check the install path if socket_vmnet was installed from source.

After:
If no socket_vmnet flags are provided minikube checks the source, brew amd64, and brew arm64 install paths for socket_vmnet.

Info:
socket_vmnet_client relative path: /opt/socket_vmnet/bin/socket_vmnet_client
socket_vmnet relative path: /var/run/socket_vmnet

source install path prefix: <none>
arm64 brew install path prefix: /opt/homebrew
amd64 brew install path prefix: /usr/local

Before:

# socket_vmnet installed via brew

minikube start --driver qemu --network socket_vmnet
😄  minikube v1.28.0 on Darwin 13.1 (arm64)
✨  Using the qemu2 driver based on user configuration

🙈  Exiting due to NOT_FOUND_SOCKET_VMNET: 


💡  Suggestion: 

    socket_vmnet was not found on the system, resolve by:
    
    Option 1) Installing socket_vmnet:
    
    https://minikube.sigs.k8s.io/docs/drivers/qemu/#networking
    
    Option 2) Using the user network:
    
    minikube start --driver qemu --network user

After:

# socket_vmnet installed via brew

$ minikube start --driver qemu --network socket_vmnet
😄  minikube v1.28.0 on Darwin 13.1 (arm64)
✨  Using the qemu2 driver based on user configuration
👍  Starting control plane node minikube in cluster minikube
🔥  Creating qemu2 VM (CPUs=2, Memory=4000MB, Disk=20000MB) ...
🐳  Preparing Kubernetes v1.26.1 on Docker 20.10.22 ...
    ▪ Generating certificates and keys ...
    ▪ Booting up control plane ...
    ▪ Configuring RBAC rules ...
🔗  Configuring bridge CNI (Container Networking Interface) ...
    ▪ Using image gcr.io/k8s-minikube/storage-provisioner:v5
🔎  Verifying Kubernetes components...
🌟  Enabled addons: default-storageclass, storage-provisioner
🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: spowelljr

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [spowelljr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[medyagh]

after adding the comments it looks good to be merged