ssh.socket is conflict of ssh.service

As you can see, in my original image, ssh.service is enabled, while ssh.socket is disabled. Now ssh.service can automatically start at booting.

But isar-cip-core enables ssh.socket, which is conflict of ssh.service.

The related configuration of ssh.socket is shown above.

Now we want to use isar-cip-core, but we do not want ssh.socket to be enabled. I don't know the enabling of ssh.socket is by design or is by mistake. If it is by mistake, it should be fixed. If it is by design, I need to know how to mask it.

Thanks.