Implements contact deletion functionality

[MasterK0927]

Resolves #13

• Adds the functionality for removing the contact from the contact list.

• Adds a button on the create page (where contacts are listed) to allow users to remove contacts from the list.

[MasterK0927]

fill="none" is needed in delete icon for retaining its transparent background behr

[mattyg]

Requested some changes inline.

One gotcha I want to make sure is handled (it may be handled already but we should confirm).

Say we have a private conversation with a contact, but we never received a profile for that contact agent and conversation. Then we delete the contact. What will be displayed as the profile name in the conversation messages, or the profile in the ConversationSummary, or in the title from the ConversationTitleStore?

[MasterK0927]

Requested some changes inline.

One gotcha I want to make sure is handled (it may be handled already but we should confirm).

Say we have a private conversation with a contact, but we never received a profile for that contact agent and conversation. Then we delete the contact. What will be displayed as the profile name in the conversation messages, or the profile in the ConversationSummary, or in the title from the ConversationTitleStore?

As per my understanding, we need to modify the delete behavior to maintain a "tombstone" record with basic display information even after deletion similar to how social media platforms handle deleted accounts.

Let me explain it in more detail.

Currently, when a contact is deleted, two key things happen:

• Contact is removed from the contacts store.
• cellId mapping for that contact is removed.

There is a potential edge case that we are surely missing. While the contact information is removed from the ContactStore , the messages in the private conversation would still exist and need to reference the sender's profile information.

If we never received a profile for that contact and then deleted the contact entry, we would lose the connection between the agent's public key and any profile information.

When trying to display profile information in conversation messages, ConversationSummary, or ConversationTitleStore, we would likely encounter one of these scenarios:

1. Looking up profile information through the contact store
   The components would find nothing since the contact was deleted.

2. Fetching profile information directly from the DHT
   There would be nothing to find since we never received a profile.

To properly handle this case, we could consider one of the following solutions:

• Keep a permanent record of basic agent information separate from the contacts store.
  This could be a lightweight store that maintains a mapping of agent public keys to their last known display information, even after contact deletion.

• Implement fallback display logic in UI components.
  This would show the agent's public key (truncated) when no profile information is available.

[mattyg]

When trying to display profile information in conversation messages, ConversationSummary, or ConversationTitleStore, we would likely encounter one of these scenarios:

Did you actually confirm this is the case? I think we may be handling it because currently messages are not included the readable for agents who do not have a profile. Not necessarily the ideal solution, but not terrible either.

If necessary I would prefer this option:

Implement fallback display logic in UI components.
This would show the agent's public key (truncated) when no profile information is available.

[MasterK0927]

When trying to display profile information in conversation messages, ConversationSummary, or ConversationTitleStore, we would likely encounter one of these scenarios:

Did you actually confirm this is the case? I think we may be handling it because currently messages are not included the readable for agents who do not have a profile. Not necessarily the ideal solution, but not terrible either.

If necessary I would prefer this option:

Implement fallback display logic in UI components.
This would show the agent's public key (truncated) when no profile information is available.

Yeah I am confirming that we have this issue, we are not actually removing the name of the contact deleted from the conversations.

[mattyg]

requested changes in comments inline

[mattyg]

Don't think this change is needed either anymore

[MasterK0927]

The ?. operator is needed here because when a contact is deleted, there's a brief moment where the contact data becomes undefined. Without ?., trying to read properties during that moment would cause an error that freezes the UI update.?. prevents this error, ensuring the deletion completes smoothly with instant UI feedback.

[mattyg]

see inline comments

[MasterK0927]

Dialog component in smaller viewports

[mattyg]

I made a few minor changes to the implementation:

• The dialog stays open while the contact is being deleted, and the "loading" indicator is shown in the dialog action button
• Show the delete icon to the dialog action button
• explicitly check if $contact is undefined once, rather than within the find callback
• Added a period to the end of the string delete_contact_dialog_message
• Added the feature to the changelog

Great work!