fix(chat): stop a sender's name flipping to their phone number

[bmc08gt]

A chat notification could name the same sender by their display name one time and by their formatted phone number the next. Two things combined to cause it.

The stored phone number depended on which chat was written last. A user's user_profiles row is shared by every chat they're in, and each member-list write replaced it whole (upsertFull, REPLACE). The server includes a member's phone number in the CONTACT_DM feed but not in the TIP_DM feed, and a full feed sync writes TIP_DMs last, so the number was usually cleared until something wrote a contact DM's members again. UserProfileDao.upsertMembers now keeps a stored phone or email when the incoming copy has none and replaces every other column as before. ChatMemberDataSource uses it for both member writes.

A side effect: if a user removes their phone number, the old one stays on their row until a chat that carries contact details sends a different one. Nothing in the member response says a field was removed rather than left out, so the row can't tell those apart.

A phone number outranked the display name. NotificationService took ContactResolver.resolveName first, and that returns a formatted number when the address book has no contact for it. Now only an address-book name (resolveContactName) comes before the profile's display name and handle, then the push title, with the formatted number last. The number stays in the candidate list so planMessageBody still strips it from a body the server prefixed with it.

The order lives in planSenderName/senderNameCandidates in SenderAttributionPlanner.kt, tested in SenderAttributionPlannerTest. The member-write behaviour is covered in UserProfileDaoTest.