Allow VisibilityCopyJob to receive either an ActiveFedora object or a Valkyrie resource

[randalldfloyd]

Descriptive summary

Convert VisibilityCopyJob to allow it to receive either an ActiveFedora based object or a Valkyrie::Resource equivalent object.

Rationale

Allow jobs to execute correctly with existing AF implementation or the Wings Valkyrie implementation.

Expected behavior

VisibilityCopyJob receives a Valkyrie::Resource and performs the action.

Actual behavior

VisibilityCopyJob raises an exception when passed a Valkyrie::Resource.

Approach for Conversion

See Pattern for Jobs Receiving Parameter that may be an AF Object or a Valkyrie Resource

Related work

These have all be modified to support AF object or Valkyrie resource using the [established pattern]((https://docs.google.com/document/d/1f9yDjtkXapFf1DYLyPhprnB4CPGaZw9p_k8T_tcor-U/edit#heading=h.qt9rxydfd727).

• Issue Allow GrantEditToMembersJob to receive either an AF object or a Valkyrie resource as the Work #4101 Allow GrantEditToMembersJob to receive either an AF object or a Valkyrie resource as the Work (PR extract out common permission job code #4123)
• Issue Allow GrantReadToMembersJob to receive either an AF object or a Valkyrie resource as the Work #4102 Allow GrantReadToMembersJob to receive either an AF object or a Valkyrie resource as the Work (PR extract out common permission job code #4123)
• Issue Allow RevokeEditToMembersJob to receive either an AF object or a Valkyrie resource as the Work #4103 Allow RevokeReadToMembersJob to receive either an AF object or a Valkyrie resource as the Work (PR extract out common permission job code #4123)
• Issue Add GlobalID::Identification for resources passed to jobs #4099 Add GlobalID::Identification for resources passed to jobs (PR automatically convert valkyrie resource to ActiveJobProxy when enqueuing #4124)

[bkeese]

This one has already been valkyrized, as of this commit:
1367040#diff-ebb7ea117a9e3897947709cd755ab906

[randalldfloyd]

@bkeese Thanks for running that one down. I'll close this with the added comment for future inspection: the reason this one works is because the downstream propagator (Hyrax::VisibilityPropagator) was refactored to allow a Valkyrie resource. That's not totally apparent at a glance for this job.