fix: phrase in-chat payments as sends, not tips

[bmc08gt]

A payment sent inside a chat showed up in the recipient's activity history as
"Tip from ".

The send side is already correct. The payment stamps
ChatMetadata.TipDmPayment.Location — TIPCARD for a tip card or deeplink,
CHAT for an in-chat send — and the server picks the activity verb from it, so a
tip arrives as "Tipped" and an in-chat send as "Sent". ActivityRow.displayTitle
discarded that verb and hardcoded the tip phrasing for both .gave and
.received.

It now reads the verb and phrases the row from it:

server verb	.gave	.received
Tipped	Tipped Sally	Tip from Sally
Sent	Sent to Sally	Received from Sally

The switch moves out of displayTitle into a static peerTitle(kind:name:serverTitle:),
matching swapTitle's testable shape, and returns nil for a non-peer row or an
unresolved counterparty so the caller keeps its existing fallback to the
server-rendered title. Swaps and every other row are untouched.

activity.title arrives already substitution-rendered on iOS, so it can read
"Tipped Bob" rather than a bare verb; the prefix match covers both, and there's
a test for it.

Analytics

The transfer events drew the line the other way: Sent Tip vs Sent Cash was
chosen by whether the target was a tip recipient, so a payment into a tip DM
reported as a tip whether it came from a tip card or the money button inside the
thread. No data was lost, since the event carried Origin: Chat, but any count
on Sent Tip that didn't split on Origin read in-chat sends as tips.

The second commit draws the same line as the feed: only a .tipcard origin is a
tip, so a send from inside a tip thread reports Sent Cash.

That leaves Origin constant at Tipcard on every Sent Tip, so the third
commit drops the parameter, the Property.origin key, and the
TipOrigin.analyticsValue mapping behind it. TipOrigin itself stays — it still
selects the payment's Location.

Net effect on the event stream:

payment	before	after
tip card / deeplink	Sent Tip, Origin: Tipcard	Sent Tip, no Origin
in-chat send to a tip peer	Sent Tip, Origin: Chat	Sent Cash
in-chat send to a contact	Sent Cash	unchanged

Existing queries that count Sent Tip without splitting on Origin will see the
in-chat volume move to Sent Cash from the release forward; historical events
keep their Origin values.

Known limit

The verb is the only signal available: activity/v1 models a peer payment as
plain directly_sent_crypto / received_crypto with no structured tip flag.
Matching an English prefix holds while the rendered title is English-only. A
localized feed would need the tip/send distinction promoted into the
notification metadata upstream.

Mirrors code-payments/code-android-app#1332.