UI Design - Folio Component Handling

Staff have identified that there are cases where folio should be collected but not within a BCOL payment record (currently staff have routing slip and no-fee). Staff have requested the option to enter folio without it being associated to a BCOL account.

We have found many inconsistencies of when/where the folio is asked for, and sometimes it is not being saved.

Actions
1. Determine PPR and MHR transactions that do not have folio options outside of the staff payment
2. Create designs to add folio outside of staff payment. Note: we should already have folio outside of staff payment for client flows which could be exposed in staff flows
3. Create rules for Folio for all app teams to be more consistent

**Grooming this work will require time and coordination across teams**

Assets Folio Requirements:
Latest version of the requirements is in Google docs at https://docs.google.com/spreadsheets/d/100Y4Adp2itr--S2THCbiNLlVICGWfXrQ/edit?usp=drive_link

Start with the linked Folio Requirements Google spreadsheet and review the PPR and MHR transaction flows, including staff payment and client flows. Inventory where folio is requested or saved, then coordinate designs and shared rules across app teams; done means the gaps, designs, and consistent folio rules are agreed.

Written by the indexing model from the issue text.