Consistently use `studyDeploymentId` rather than `deploymentId` about carp.core-kotlin HOT 2 CLOSED

A couple of remarks in regards to current class naming, before deciding on changing anything:

• The subsystem is called deployment.
• The deployment subsystem deals with all logic pertaining to deploying a StudyProtocol. What this means should be clear by now (instantiate a protocol, which corresponds to one participant in a simple smartphone study), and we still have not identified a better name for this.
• A StudyDeployment is a single instantiation of a StudyProtocol. This is a domain object, thus encompassing business logic.
• DeploymentManager is an application service of this subsystem, relying on StudyDeployment internally to execute deployment logic, but StudyDeployment is not exposed through its interface.
• DeviceDeployment is a DTO returned by the DeploymentManager, but constructed by StudyDeployment, containing the subset of relevant deployment information for a single client (another subsystem) defined in the study protocol.

from carp.core-kotlin.

• Will rename DeploymentSnapshot to StudyDeploymentSnapshot, since it is a snapshot of StudyDeployment.
• Will rename DeviceDeployment to MasterDeviceDeployment, since it only master devices receive them.
• Will rename DeploymentStatus to StudyDeploymentStatus, to more clearly disambiguate between the upcoming 'client status' or 'master device deployment status'.
• Will rename functions and parameters in DeploymentManager and related classes and test classes to match the above changes.

from carp.core-kotlin.