Add Jinja 2 for templating #4
Description
Right now, the JSON values for things like extensions.json are hardcoded into the code and then dumped to a file using the JSON module. This is probably not eggregiously wrong, but as devwrangler scales and starts to spawn additional files (or allows users to provide us with additional files) I'm certain we're going to want to have more flexibility and extensibility.
In my mind, the right solution here would be to add Jinja2 as a dependency and then maintain a folder of template files in the CLI's source directory. We could then add some very basic logic to the templates to determine what should or shouldn't exist as a feature or dependency when a user spawns a project while cleaning up our code considerably.