Enable multiple environments for a single project

[willbakst]

Description

We should support running generations that route to a dev environment during development but route to the production environment once deployed.

I'm thinking something like a LILYPAD_PROJECT_ENV environment variable would work? Kinda like NODE_ENV. This way a single project could have multiple environments.

We'll need to update everything to link to a new environments table most likely.

[willbakst]

If the goal is just to be able to point the same repo to different projects, then the updates in #70 will make this immediately possible.

However, if the goal is to have different environments for the same project, then we'll need to implement new functionality around environments. In this case, the versioning will remain consistent agnostic to an environment but the trace data will be scoped to the environment. This could also be as simple as adding tags/metadata that we can later filter over.