Having this file was causing double rendering of bulkrax links in the sidebar.

Issues:
- #1850
- scientist-softserv/hykuup_knapsack#111

Update bulkrax to point to hyrax-4-valkyrie-support

This commit will adjust for the changes introduced in this commit:
samvera/hyrax@8fc0894

bulrax_identifier is not a required property. Each client should set their desired source_identifier in their application.

Issue:
- scientist-softserv/hykuup_knapsack#136

This commit will add a decorator to check the `human_readable_type` of
the given object is a Valkyrie migration object (which by convention
ends with 'resource') and adjust the generated link accordingly.  For
example, a GenericWorkResource should generate links like
`/concern/generic_work_resources/...` instead of
`/concern/generic_works/...`.

The models were updated to include the Hyrax::NestedWorks so the `Attach
Child` button would populate the appropriate work types.

Lastly, the `Gemfile.lock` was updated to include the latest version of
Hyrax `double_combo` branch.

For us to leverage the useful shared specs of Hyrax, we need a test
adapter.

…ifier-to-bulkrax

I903 remove bulkrax_identifier dependency

Using 'human_readable_type' was going to be flemsy.  Instead we are
opting for adding the `valkyrie_bsi` to the index and asking that.

…tion

We configure Bulkrax to use the `ValkyrieObjectFactory` along with the
`ValkyrieMigrationCoercer` so a `GenericWork` will create a
`GenericWorkResource`.  Also, updated the revision of Bulkrax.

…on' into i35-valkyrize-hyku

This reverts commit d9fa1a2.

This reverts commit 887fbf2.

Ideally the code would reference the SolrService in one manner.  This is
an effort to create an insulating layer around that.

♻️ Favor Hyrax::SolrService

Not all applications will use bulkrax_identifier as their source_identifier. This code makes it more dynamic.

TODO: Make Wings::CustomQueries more dynamic

…into i35-valkyrize-hyku

ref:
- samvera/bulkrax@29f2264

This reverts commit 78d26c5.

find_by_source_identifier files were moved into bulkrax.

specs refer to object as @object, and thus caused a lot of spec failures without this.

This commit will make sure that the set child flag transaction fires
when ingesting with Bulkrax.  Also fixed a weird bug where the extra
space in the query was causing the query to fail.

🧹 Fix relationship links

AF's member_ids returns an array of ids so mapping (:id) will not work.

Pull in fixes to make bulkrax relationships work for valkyrie. It also fixed the setting of is_child and the linking of relationships

Related:
- samvera/bulkrax#908
- scientist-softserv/iiif_print#328

Per Rob, remove HYKU_IIIF_PRINT conditional. Iiif print will be enabled by default.

This commit adds reindexing for Valkyrie objects.

Issue:
- scientist-softserv/hykuup_knapsack#146

Co-Authored-By: Kirk Wang <k3wang@gmail.com>

Issue:
- scientist-softserv/hykuup_knapsack#71

Co-Authored-By: C Barton <43180845+CB987@users.noreply.github.com>

* main:
  Appeasing Rubocop
  override gems from knapsack with bundler inject

remove HYKU_IIIF_PRINT conditional

Co-Authored-By: C Barton <43180845+CB987@users.noreply.github.com>

This spec is no longer needed as its relevant code moved into bulkrax.

ref: add a reindex after the child work has been saved.
- scientist-softserv/iiif_print#332

The `show_pdf_viewer` and `show_pdf_download_button` fields were showing
up on the form even though in the yaml they were set to false.  It looks
like just removing the `form` key from the yaml file will prevent them
from showing up.  Also updated the `Gemfile.lock` file.

Restricted is the visibility, registered is the concept.  This fixes
that misnomer.

See
https://github.com/samvera/hyku/wiki/Updating-Hyku-6-with-Hyrax-5-Developer-Notes#access-control-list-acl-considerations

Grab the latest sweet sweet double combo

The factory is directly copied from Hyrax; and is not fully functional,
but it's better than what we've got.

Also refactor to set the default work type for Bulkrax later in the
application boot cycle.  When it was where it was at, I encountered
issues with wings model registration.

Favor the Lazy migration strategy

By extending the ability class to include all of the collection models,
we open up some additional considerations.

This does involve fixing a bug that is masking another underlying bug.

This commit will add an elsif statement to the wings adapter to handle
FileSet objects. It will also add the configuration for IIIF Print to
use the IiifPrint::PersistenceLayer::ValkyrieAdapter.

This commit will update the Hyrax and IIIF Print revisions which should
allow us to ingest images and have it render in the UV.  Uploading a PDF
should also work but PDF splitting current does not work.