don't force "Collection" model filter from the view

the search builders for the target controller already search effectively for the
model class, and may have better strategies for doing so in the future. adding a
filter here prevents applications from using Collection models not named
"Collection".

app/views/hyrax/admin/collection_types/index.html.erb

@@ -40,7 +40,7 @@
                  <% unless collection_type.admin_set? || collection_type.user_collection? %>
                   <button class="btn btn-danger btn-sm delete-collection-type"
                           data-collection-type="<%= collection_type.to_json %>"
-                          data-collection-type-index="<%= hyrax.dashboard_collections_path({ 'f[collection_type_gid_ssim][]' => collection_type.to_global_id.to_s, 'f[has_model_ssim][]' => 'Collection' }) %>"
+                          data-collection-type-index="<%= hyrax.dashboard_collections_path({ 'f[collection_type_gid_ssim][]' => collection_type.to_global_id.to_s }) %>"
                           data-has-collections="<%= collection_type.collections.any? %>">
                     <%= t('helpers.action.delete') %>
                   </button>

spec/factories/hyrax_collection.rb

@@ -26,7 +26,7 @@
     after(:create) do |collection, evaluator|
       if evaluator.members.present?
         evaluator.members.map do |member|
-          member.membner_of_collection_ids += [collection.id]
+          member.member_of_collection_ids += [collection.id]
           member = Hyrax.persister.save(resource: member)
           Hyrax.index_adapter.save(resource: member) if evaluator.with_index
         end