Move views to code and remove dependency on NVelocity


The 3 existing templates are practically code already. Since we will be supporting non-reboot updates, and since these views wouldn't normally be changing frequently at run-time anyway, we may as well have the various benefits of actual compiled code (such as speed, step-through debugging, test-readiness, and so on). This will allow us to also eliminate the complexities of the additional component/dependency.

These code view providers should use an interface for MEF discovery, to help prepare them for non-reboot updates (where the referenced view provider gets replaced with a newer one after a new DLL got dropped into the server'r running directory).

Alternatively, if we decide to keep the template system instead, we'll need to restore documentation about how to work with those, how to get syntax highlighting for them, how to effectively debug them, etc.