Add dashboard to /as/

The dashboard is a temporary solution to Keystone's shortcomings. Because of this, not a heck of a lot effort will be put into making it clean. It exists solely so AtriumScreen can be tested properly while Keystone is developed.

It currently allows for new pages to be defined using atriumscreen.navDash - an array of page names
To define new routes, simply use atriumscreen.on('keystone routes'). Routes here are relative to /as as well
Use res.admin(view, locals) in this to render to the admin UI
You can fill res.locals.scripts and res.local.styles with files you need to link to.

It ain't clean, but it works.
Allow custom scripts and styles in layout controllers

Is simple, just append elements to the res.locals.styles and res.locals.scripts arrays. Please use .push and don't just set them so as to not interfere with middleware.
In the future, there is a plan to stop the usage of two of the same script. Using Bower to do this programatically is probably the best way forward.
Add support for a refresh time

The window will automatically refresh based on the date loaded in res.clientData.as.refresh
The calendar decider automatically populates this based on the current event
There is not currently support with calendars working in tandem in this regard
Remove decision stacks

Cannot warrant having a separate data model for decision stacks, so now they are just arrays inside the screen itself. This makes one less step for setting up.