Fetching "real" data for multiple select-inputs, like categoryCombo, optionSets, mapLegendSets, etc.

Only resolving for CREATE at the moment, for testing reasons.
dataElementService.getElement() now utilizes the getAllElements() method to get the requested item;

The reason is that we think it's better to get all of the waiting\loading done before the app is further used; This way there will only be minimal loading later in the app. This is only a downside if the app is initialized on a route requesting a  single element; In normal, getAllElements() would be used anyways.

 Also fixed route.resolve for clone to remove ID of the cloned object, so it's truly a NEW clone, and not the exact same element.
Critical bug fixed: Cloning an element would edit the original copy, instead of a copy; This is fixed with angular.copy();

Added a third option for the edit view's title: "Cloning data element: " xxx; In addition to "Creating new data element" and "Editing data element: " xxx.
Commented a few things, and made small tweaks;

comments are for guidance for everyone to know what's left out of the code still.
Added directive template for loading;

Added app.config for checking active requests and determining if the app is loading\waiting for requests.
Added loading-gif; css-class for loading,updated directive and tweaked it to fit on the app. Let's hope it looks ok in DHIS2 on other monitors aswell :P
Added simple animations for changing views :)
Loading text changed to something more amusing :)
Moar animations; This time for edit view; Too much? :S
Merge pull request #3 from henninglh/Routing-and-resolves

Routing and resolves