Pass specific coniguration to environment instead of bare deployment JSON

Instead of using the shape of the deployment.json provided by a protocol deployment, we should pass more specialized configuration object to the Environment. This would then allow us to provide custom token names, exchanges, etc. in a more controlled fashion. External systems, like our own frontend, can then do the job of translating a deployment file to this configuration object.