Add guardrails around classes like VmrInfo for their usage before initialization

PCS supports multiple vmrs (dotnet/dotnet, dotnet-dotnet, maestro-test-vmr...).
We create a scope for every job PCS processes.
The issue with these two facts is that, at the time of creating the scope, we don't know which VMR the subscription wants to use. Because of this, we have classes like `VmrCloneManager` which are reponsible for making sure we use the correct VMR, and refreshing the metadata classes (VmrInfo, SourceManifest, etc..) with the current VMR data. The issue with this approach is that these metadata classes shouldn't be used before they're refreshed with the latest VMR data.

We want to add some kind of exception throwing guardrails that will help prevent incorrect usage of these classes