The idea is to provide an standalone launcher for TC mods, this would be able to allow TCs like WCS to have a launcher were they could redistribute their mod and provide updates using Nebula.

This will have to come after #232 because this only makes sense with a portable mode folder structure.

The idea is to have two possibilities here, hardcode customization data were all data is directly added to CustomLauncher.cs OR an additional file next to the config file with the customization data that gets loaded on startup. This last option would still allow for normal launcher updates from the main repo, while hardcoding the customization data can only support updates from a forked repo.

The other requierement is to keep extra added code and views to the minimun so the added support overhead is minimum. The idea is to still use the same views for things like global settings (engine settings here), mod details, mod settings, mod install... maybe the nebula login so this could work with private versions too...
The only view added should be the alternative main one.