Load jinja Environment lazily and cache it

This avoids a circular dependency when a project's jinja Environment is declared at the module level and depends on django settings (since django-viewlet previously imported the Environment at project startup).
Merge pull request #20 from heyman/env-dependency-fix

Load jinja Environment lazily and cache it