systemd socket and service conflict?

### Checklist

- [X] This is a bug report, not a question. Ask questions on [discuss.ipfs.io](https://discuss.ipfs.io).
- [X] I have searched on the [issue tracker](https://github.com/ipfs/go-ipfs/issues?q=is%3Aissue) for my bug.
- [X] I am running the latest [go-ipfs version](https://dist.ipfs.io/#go-ipfs) or have an issue updating.

### Installation method

built from source

### Version

```Text
go-ipfs version: 0.4.17-
Repo version: 7
System version: amd64/linux
Golang version: go1.10.3
```

### Config

_No response_

### Description

When I installed the systemd .service and .socket files from [the systemd directory](https://github.com/ipfs/go-ipfs/tree/master/misc/systemd) as system files, the sockets prevented the service from starting since they bound up the listening ports. journalctl showed systemd trying over and over to start go-ipfs, always failing with that error.

This meant go-ipfs did not restart on reboot.

I don't understand systemd well enough to fully troubleshoot this.

Maybe there's an error in the provided files? Or maybe I shouldn't have installed the socket files if I'm installing the service as a system service instead of a user service? In that case, it would be nice if the documentation in the parent directory had a note warning not to install the files.

It sounds to me like the .socket files were expected to work, though, since #6675 talks about socket activation.

Either way, whether it's user error or something needing tweaking in the systemd files, I wanted to report this issue getting the daemon going on startup.