split VLsetup into manager and module

Small thing but VLsetup in the new system should technically be renamed VLManager for naming consistency, although this may break existing scripts so may not be worth it. Also it may be worth splitting out VLSetup's behaviour into a separate VLModule such that functions used by all containers inherit from VLModule. Manger spefic behaviour (analytics, calling RunJob etc..) can then be spun off separately into VLManger/VLSetup.