removed all json responces from guidances controller and forced authorization

removed authorization from home-controller as some users will not be logged in when request fielded

forced auth on organisations_controller. TODO: re-check parent, children, and templates after AJAX removed

modified organisations

added auth to home controller

removed verify_authorized out to individual controllers

forced all actions to be authenticated through pundit

removed unused actions and json from users controller

added ability to grant permissions to other users

overhaul of performance of users admin-index

added new permissions to api

removed cancancan and rollify

implimenting auth changes in the views

bugfixes to auth

finished implimenting new authorization scheme in dmptemplates

updated authorization for all controllers ...

-changed from passing through records as feature not supported
-changed 403 error to better reflect what's happening
-added scope to many of the indexes
-added organisation-scope to requests from old org-admin roles
-renamed guidance_groups_policy to guidance_group_policy.rb

added default redirect to 403 page for unauth

added pundit auth to dmptemplates controller

added pundit auth to guidance groups

added pundit auth to guidances

bugfix to ensure organisations auth working

removed depricated controller

added pundit auth to organisations controller

added pundit to users controller

added pundit authorization to users

proof of concept for pundit ...

-got the pundit policy file working
-verified that it blocked/allowed users with correct permissions
-fixed a bug in user model where the magic strings had been poorly defined
-

installed new gem pundit

super_admin area for languages, changes to langauge initializer to fix migrations issue and org language priority in user language picking

Merge branch 'development' of https://github.com/DMPRoadmap/roadmap ...

Lots of merge conflicts so I had to go through and manually fix them

Hopefully have not missed any conflicts nor destroyed any work done by somebody
Most of the conflicts were on account of changes to branding in files, but
others were content changed on both forks

New Gem requires ruby 2.2.2 (contact_us)

fix locales picking