Fix demographic polling translation strings
Load user data in root-controller resolve

Some views would require user data and error if
the getUser() promise had not resolved by the time
they needed the user data.

Resolve in the root-controller ensures necessary data
available for all views, since all logged in views inherit
from rootController
Set new scenario button inactive if form invalid
Return proper frequency values in trip response
Add missing translations for settings/scenarios
Add frequency to new/edit route scenario view

Also ensures that a valid route and trip are
set when the route-edit -> route-stops transition
occurs. (Regardless of whether new or edit route was
originally selected)
Fix broken angular tests

Moving the getUser to the root-controller resolve required:
No longer make a getUser() API request on app load
Stub the user provider for the root-controller
Merge branch 'feature/trip-cleanup' into develop