Add capability to print a single request, whether or not fulfilled

[cielf]

Summary

Add the capability to print a 'picklist' for a single request, whether or not fulfilled.

Why?

Request from bank -- their workflow is schedule the distribution, then go and pick the stuff.

Details

Add a button on the bank's view of a request that will print the request in picklist format. Look at the "Print Unfulfilled Requests" functionality on the bank's "Requests" list for what that's like.

Criteria for completion

• functionality as described above
• tests to support that functionality
• update the user guide to reflect the new functionality

[bsbonus]

@cielf can I take this? I definitely have some questions in regards to some details, but mostly is straight forward

[cielf]

It's yours!

[bsbonus]

@cielf WIP mostly have this done, but noticed a few things I could either include/exclude from the PR. It's just options for you, none of it is dealbreaking from a code standpoint IMO.

1. Added test coverage to the existing "print_unfulfilled" action, since this new one is supposed to mostly mirror that. Want that in? There was some stuff already there.
2. See screenshots for the proposed buttons on the list and detail pages for donation requests. The list page looks a little crowded & not aligned IMO, but I would vote for a separate PR to change that into a dropdown button or something that cleans up the column.

3. The "print" & "print unfulfilled" buttons both open the link in the same browser tab...shouldn't that be a new tab with target=__blank? Just a detail I noticed in testing.
4. I'm blocked on updating the docs until the design is locked -- see question 2.
5. It's a little unclear how the "requests" move to "discarded" state. Cancelling doesn't move them there, so wondering if this is dead functionality?

WIP PR: #5188

[cielf]

1. I'm a fan of more test coverage.
2. I agree - we could make that a "good first issue" for someone down the road, but it's not necessary now.
3. Hmm -- I think we currently have all the prints open in the same browser tab. If we were to change them, we would want to change them all. I can take that to the users to ask if it would be more convenient.
4. See answer 2
5. I'll need to poke into that a bit more -- I see requests with status 3 and a "discarded at" field in the production data as of this past week. Maybe the filter is broken?

[cielf]

5 (continued). Yeah -- it looks like we specifically are only grabbing the undiscarded ones for this. There really isn't any way for the banks to find the cancelled ones through the UI. Another thing to bring up at the next stakeholder meeting. So we should probably remove "discarded" from the filter, unless there is a need. But that, too, would be a separate issue.

(note: you can view them if you put replace the id in the URL. )

[bsbonus]

@cielf okay -- if you're happy with the buttons as it stands today, I can wrap up this PR by adding the updates for the docs

[bsbonus]

@cielf PR is updated and ready for review: #5188

There were some odd things RuboCop decided to lint -- I called them out in the comments, but I don't remember modifying those files.

[cielf]

@bsbonus Hrm. It's possible it's a result of the very recent upgrade to Ruby 3.4 -- I'm not sure, though.