Fixing issue with error when deleting contact from appeal.

[dr-bizz]

Description

On appeals, when deleting a contact from an appeal, it would sometimes error. This PR fixes this bug.

The issue arose as I added functionality that tested the contact in question is on the appeal. However, since it meant we had to load all the contacts before we deleted it, if the user clicks the "Remove" button before it all loads, it would cause this error.
I could have prevented the "Remove" button from being selected until all contacts were loaded or removed the functionality and let the server check and produce the error. I opted to remove it as it adds a better UX, and as a bonus, there's less code to manage.

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]

Preview branch generated at https://hs-1256989.d3dytjb8adxkk5.amplifyapp.com

[github-actions]

Bundle sizes [mpdx-react]

Compared against 9d1180c

No significant changes found

[canac]

Do you mind putting a link to the HelpScout ticket in the description and putting the ticket number in the title?

[canac]

@dr-bizz Does this work for you? I'm getting errors like AppealContact with id=2c10008b-784e-4540-8cb8-297022f9b473 not found in preview. I think it would be best if the API accepted a contact id, but it seems that it's looking for a contact-appeal id from the join table.

[dr-bizz]

Yeah, I think you are correct. it's looking for an ID that joins the contacts for the appeal, rather than the contact ID. I will fix it. I might talk to the backend team about making the API accept a contact ID

[canac]

I might talk to the backend team about making the API accept a contact ID

@dr-bizz I'd recommend that if they have capacity. In most cases, I don't think that the API should make clients deal with join ids.

[dr-bizz]

The backend will be adding the contact ID to GraphQL. so I will be closing this PR and will open a new one when I need to update this mutation.