CRUD operations for Organizations

HYDRASIR-97
HYDRASIR-151 #close
HYDRASIR-152 #close
HYDRASIR-155 #close
Create a persisted organization model

HYDRASIR-97 #close
Add more organization_spec tests.  Tidy up error processing in organizations_controller.   Tidy up code in Organization class.

[skip ci]
Make use of CollectionModel.
Merge pull request #416 from projecthydra/feature/HYDRASIR-97-Organization

CRUD operations for Organizations
Create a Repository Manager role

Create a 'manager' method in base.rb that reads a list of manager
email addresses from config/manager_usernames.yml. Modify ability.rb
to check that the current user is a manager and grant
edit/update/destroy access on everything except users/profiles.
Modify curate_generator.rb to create a default yaml file.
(Editing other users and making everything discoverable will be done
in future stories)

HYDRASIR-201 #close
HYDRASIR-202 #close
Merge pull request #421 from projecthydra/feature/HYDRASIR-95-create-repository-manager-role

Create a Repository Manager role
Updating VERSION
Pinning Rubydora version to 1.6.5

Pinned the Rubydora version to 1.6.5 until we can configure
soft_delete to work with Rubydora versions greater than 1.7.0

HYDRASIR-236 #close
Make partial matching work for keyword and autocomplete searches

    To enable partial matching for various search types, the use of
    EdgeNGram filters were employed in the SOLR schema. This was
    accomplished in a way that also adds configurability into the
    search system. This was not only desirable but necessary in order
    to constrain the use of edge filtered fields to specific use cases
    so as to not introduce unpredictable behavior. Configurability
    means that:

   - a new generator named curate:search_config changes SOLR
     schema and config files based on user questions

   - a configurable Yaml file (config/search_conig.yml) is used at
     start that makes a hash available to controllers involved in SOLR
     searches. This Yaml file is changed by the curate:search_config
     generator to reflect SOLR config options.

    Changes in this commit:

   - Create curate:search_config generator in search_config_generator.rb
     that edits SOLR schema and config files based on user questions.

   - Modify curate_generator.rb to create initial search_config.yml file.

   - Modify curate_generator.rb to write new lines to curate_initializer.rb
     that will initialize search_config hash from Yaml file.

   - Modify catalog_controller.rb and people_controller.rb to change hard
     coded search options to read from initialized search_config hash.

  - Modify configuration.rb to create accessors so that hash from
    Yaml file is available as Curate.configuration.search_config

  HYDRASIR-14 #close
  HYDRASIR-15 #close
Merge pull request #422 from projecthydra/feature/217-rubydora-bug

Pinning Rubydora version to 1.6.5
Merge pull request #425 from projecthydra/feature/14-15-configurable_partial_match_searches

Make partial matching work for keyword and autocomplete searches
Works around UI bug causing multiple delete confirmation dialogues

Problem is caused by Turbolinks links incompatiblities.  Remove from curate_vanilla Application.

HYDRADIR-180
Renaming Organization to Hydramata::Group

Provide Read/Edit access to members of the group.
Merge pull request #427 from projecthydra/feature/183-rename-organization-to-group

Renaming Organization to Hydramata::Group
Merge pull request #426 from projecthydra/feature/HYDRASIR-180-Double_Delete_Item_Confirmation

Works around UI bug causing multiple delete confirmation dialogues
This closes https://jira.duraspace.org/browse/HYDRASIR-225 which contains 4 bugs:
https://jira.duraspace.org/browse/HYDRASIR-145 Continual dialogue box won't allow delete to work
https://jira.duraspace.org/browse/HYDRASIR-179 In Chrome the add and remove buttons are duplicated in many of the fields
https://jira.duraspace.org/browse/HYDRASIR-180 Double delete item confirmation
https://jira.duraspace.org/browse/HYDRASIR-144 Menu doesn't work sometimes
All of the above issues have been tested in FF, Chrome, IE, Safari with TurboLinks disabled.
Disable requiring TurboLinks in the curate app generator.

By disabling TurboLinks, several user interface issues involving javascript are resolved.  This fix addresses any future applications generated from Curate.  Applications already generated from Curate will need to remove this line from their application's /app/assets/javascripts/application.js file:
             //= require turbolinks

HYDRASIR-145 #close
HYDRASIR-179 #close
HYDRASIR-180 #close
HYDRASIR-144 #close
HYDRASIR-225 #close

[ci skip]
Merge pull request #429 from projecthydra/feature/HYDRASIR-225_Fix_these_bugs-Disable_TurboLinks

Disable requiring TurboLinks in the curate app generator.
TurboLinks issues fixed in a different way that does not exclude TurboLinks

1. Re-enable requiring TurboLinks in the curate app generator.
2. Move javascript include tag for application.js from the body to the head of the boilerplate.html.erb.
Merge pull request #431 from projecthydra/feature/HDYRASIR-225_Fix_TurboLinks_problems_again

TurboLinks issues fixed in a way that does not exclude TurboLinks