Made a major mess. Started to straighten out scopes & responsibilities.

I'm currently working out scopes and assignment of
dashboard/services/pulldowns/navs/editors/everything else and
controllers and in general I'm changing and modifying way too much
at once. But currently, this is like a giant ball of yarn, start pulling
on one end and the entire thing comes your way.

As a whole, I just want to load the dashboard into a scope where all
the parts of the dashboard management can access their specfic parts
of the dashboard, but currently, this is harder than it looks. I'll
keep digging though.

I'm just scared to merge all of this and I probably won't issue a
pull request until I have tested this internally for a week or two
while keeping up with upstream. Anything else would be way too
annoying to work with.
Moved edit_path to panel-objects / row controller

I wanted to get rid of that functionality in the dashboard provider, so
my dashboard provider only loads and provides dashboards. The most
reasonalbe place to put it would be the panel/pulldown objects, so I
placed it at least into the panel objects. I'll need to see if I can
place the whole thing into the pulldown objects, since they are loaded
from elasticsearch. I'll also need to check saving panels back to
elasticsearch.
Everything but dashboard Loading -> dashCtrl

I feel like this is the right direction here. Moving the functions like
this, I can separate the actual dashboard loading & creation from
setting up the default dashboard wiring.

Effectively, this gives us freedom in two directions: For one, we can
have multiple controllers & services for retrieving or generating
dashboards, and we can have multiple dashboard controllers for different
view and ways to handle a loaded dashboard.