MPDX-7955 ecreate Flows and Implement Contact Move Functionality

[dr-bizz]

Description

In this PR, I added the column switching functionality to the flows view.

You can view the changes in this PR like so:

• Setting up the page for functionality when moving user
• Exclude Functionality
• Asked Functionality
• Committed Functionality
• Received Functionality
• Editing functionality on Flows to ensure it all works.
  • Removing selectedFilters prop as no longer needed
  • Fixing mistake with status on the contact
  • Making own version of FrayLayer and RowPreview as status value is different.
• Given Functionality
  • Update Donations Modal
  • Writing tests for update donations
• Writing test to ensure everything works as it should

I will be adding the following functionality in up coming PRs.

• refresh columns after moving contact.
• Prevent contact from going to specific columns.
• Select all functionality

Checklist:

• I have given my PR a title with the format "MPDX-(JIRA#) (summary sentence max 80 chars)"
• I have applied the appropriate labels. (Add the label "On Staging" to get the branch automatically merged into staging.)
• I have requested a review from another person on the project

[github-actions]

Bundle sizes [mpdx-react]

Compared against c2b3d21

Dynamic import	Size (gzipped)	Diff
../src/components/Contacts/ContactFlow/DynamicContactFlow.tsx -> ./ContactFlow	60.42 KB	+1.58 KB
../src/components/EditDonationModal/DynamicEditDonationModal.tsx -> ./EditDonationModal	76.67 KB	+1.05 KB
../src/components/Tool/Appeal/Flow/DynamicContactFlow.tsx -> ./ContactFlow	60.42 KB	+1.58 KB
../src/components/Tool/Appeal/Modals/UpdateDonationsModal/DynamicUpdateDonationsModal.tsx -> ./UpdateDonationsModal	104.92 KB	added

[canac]

Just a few style suggestions I noticed, but this is really good! I'm a little concerned that we had to copy/paste the DonationTable component, but it would probably be fairly difficult to refactor it into a generic component that can be used in both places.

[canac]

I assume this component is too different from the existing DonationTable to reuse it?

[dr-bizz]

I think so. It can probably be done, but the component might then become too confusing. Maybe this is something we can flag for post-switch to investigate.

[canac]

I think it's good as-is for now.

[dr-bizz]

I'm a little concerned that we had to copy/paste the DonationTable component, but it would probably be fairly difficult to refactor it into a generic component that can be used in both places.

So this is what I initially did, but since it got so complex and I needed to move queries and functionality to the parent component, I had to switch to using my own table.

[canac]

I don't think you've changed anything since I reviewed last. Still looks good! I agree about the donations table. Sometimes duplication is better for components that serve different enough purposes.

[dr-bizz]

This PR was merged into production. something weird happened when I merged it and it think's it was closed.