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
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.
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]
Cleaning up browse everything related changes. Removing unused js file and view clean up