Configuring mvnd.socket in unix mode cannot generate a socket file

### Affected version

1.0.2 and 2.0.0-rc-3

### Bug description

I am using version 2.0.0 - rc - 3 and 1.0.2 configured mvnd.properties file content, mvnd.socketFamily = unix and mvnd.socket = / enterprise/mvndSocket/daemon.sock, However, after starting the daemon, I checked the status and found that only the configuration of mvnd.socketFamily was effective, while the configuration of mvnd.socket was not. The generation of the socket file was rolled back to the temp in the root directory, which was not what I wanted

Start by tracing how mvnd.socket and mvnd.socketFamily are read and applied during Unix daemon startup. Reproduce the issue with the reported mvnd.properties settings and verify that the daemon creates and uses the configured socket path rather than a temporary root-directory path.

Written by the indexing model from the issue text.