End to End Testing: Send recall request- related notices (user initiated)

Context
Recall requests include items that are currently checked-out by another patron (Patron A). Recall requests typically ask Patron A to bring the item back before it's original due date/time. This differentiates it from a hold request where Patron A cannot renew the item. Once the requested item is returned, it is routed to the requested location, if necessary, and then placed on the hold shelf.

The recall request process prompts several patron notices. Specific notices are outlined below.

For each of these scenarios, exact timing and conditions are determined by a combination of notice policies and circulation rules, and exact wording is determined by templates. Each of these specific scenarios may or may not be used by every institution. If there's no corresponding policy defined in settings, then these scenarios won't apply.

Scenario 1
Given an item with a status of checked-out
When it is recalled
And there's a matching circulation rule, notice policy and template
Then send a request confirmation notice to requester (Patron B in diagram)

Scenario 2
Given an item with a status of checked-out
When it is recalled
And there's a matching circulation rule, notice policy and template
Then send a recall notice to patron (A in diagram) that currently has it checked-out (typically contains information about new due date/time - in most cases, sooner than the original due date/time)

Scenario 3
Given a recalled item
When a FOLIO operator (or patron) cancels the request
Then send a cancellation notice to requester (Patron B in diagram)