Lock file enhancement: Add unique tag to modules

In the initial implementation of the IPM lock file, the module definition has `name`, `version`, `repository`, and `dependencies` properties. We should add some sort of unique tag that goes along with the module that lives on the repository. The reason for this being is a scenario that a module gets replaced in a repository with a new artifact. This would lead to installing from a lock file using a different module artifact than what was on the environment the lock file was created from.

Example:
- `my-module v5.1.0` from `my-repository` is installed on instance-1
- Lock file gets created
- For some undefined reason, `my-module v5.1.0` has its artifact replaced on `my-repository` that has differences from the original `my-module v5.1.0`
- Lock file gets installed on instance-2

In this example, nothing would explicitly error, but our expectation would be for instance-1 and instance-2 to be identical when they are not

Blocked by #281