Decoupling the strong relation between Contracts and Utils

Issue

Simple view of the infrastructure components

Currently, all projects that depend on Contracts have to be updated only for a small change in Utils, since otherwise, a NuGet version conflict will occur.

Solution (proposal)

In an effort to make these dependencies more friendly with the development pipeline, we looked at different scenarios but found that keeping the current references was the cleanest way if we want Utils to be separated from Contracts. So the proposal is to refine our mainline approach, so we can get to a point in the repositories where we could start analyzing the use of version ranges on our NuGet references.