Visibility assignments getting switched in Curate prod

[eporter23]

Describe the bug
While reviewing recently created test objects, I am finding that works set to Private are getting assigned as Rose High view. I also see that the original visibility assignments were "restricted" (aka Private) and to my knowledge, I have not changed the visibility settings, because this is production data and test objects should always be set to Private.

To Reproduce
Steps to reproduce the behavior:

1. Go to Curate prod
2. Navigate to this work: https://curate.library.emory.edu/concern/curate_generic_works/634sj3v2mc-cor?locale=en
3. Note that the work's visibility shows Rose High View
4. Edit the work and change its visibility to Private
5. Save the changes
6. See the confirmation message that the work has been edited
7. See that the Private visibility has not changed and still shows Rose High View
8. Scroll down to the Preservation Events section of the View Work page, and click on View More Detail

Expected behavior
A clear and concise description of what you expected to happen.

When a visibility assignment of Private is assigned, the visibility should not switch to Rose High View.

Screenshots
If applicable, add screenshots to help explain your problem.

Editing the work to re-set it as Private:

Original access control set as "restricted"/Private

No changes after the Edit to change visibility:

[bwatson78]

Good news is that the params are definitely passing through restricted. So it must be the controller action not working as expected. Looking...

[bwatson78]

Within Hyrax logic, an object only responds with private visibility if the read_groups it is assigned with is nil. I may have circumvented a necessary step for this object to have been assigned via the UI yesterday with the methods I performed in this ticket: #2407.

Anyways, I have assigned this work's #read_groups to an empty array, and it's now showing Private.

[eporter23]

I'm seeing the badge for Private on that work now, but the manifest is displaying content. For Private works, we should just see a blank UV. Example of a Private work in test: https://curate-test.library.emory.edu/concern/curate_generic_works/3009w0vtdw-cor?locale=en

[bwatson78]

I'll attempt a manifest regen. I didn't before and I think you're still seeing the cached manifest with Rose High assigned.

[bwatson78]

The non-UI, hacky changes I made to that work in #2407 didn't kick off a callback to copy the new visibility over to the work's file_sets. Doing that now.

[bwatson78]

That's done, as well as a new manifest regen. It's now just a blank screen.