[Android] Paired community shows ID suffix instead of Desktop community name

## Summary

After pairing Buzz Mobile on Android with an existing community, the mobile community list displays the community ID (or its final characters) instead of the human-readable name configured in Buzz Desktop.

The community is named **CoRo** in Desktop, but the paired Android client does not display **CoRo**.

## Environment

- Mobile device: Google Pixel 10 Pro
- Mobile platform: Android
- Buzz Mobile version: unknown
- Desktop platform: Windows 11
- Buzz Desktop version: 0.5.3
- Community: self-hosted Buzz relay on a remote VPS
- Pairing completes successfully and the community is accessible

## Steps to reproduce

1. Connect Buzz Desktop to a community.
2. In Desktop community settings, set the community name to **CoRo**.
3. Pair Buzz Mobile on a Pixel 10 Pro with that Desktop/community.
4. Complete pairing and open the community list on the phone.
5. Observe the label shown for the paired community.

## Actual behavior

Buzz Mobile displays the community ID, or the final characters of that ID, as the community label.

## Expected behavior

Buzz Mobile should display the human-readable community name **CoRo**, matching the community name shown in Buzz Desktop. The stable ID may be shown separately for diagnostics, but it should not replace the user-facing name.

## Impact

A successfully paired community appears incorrectly named on mobile. This becomes especially confusing when a user has multiple communities because IDs are not meaningful or recognizable labels.

## Related issues

- #2797 — community names remain device-local rather than syncing from the relay
- #6766 — mobile community naming and other mobile/desktop parity gaps

This report isolates the observed Android pairing/display behavior: pairing succeeds, but the resulting mobile community entry falls back to an ID suffix instead of the Desktop name.

Start by tracing the Android pairing flow into the community-list display, then compare how the paired community name from Buzz Desktop is represented versus the ID suffix. Reproduce with the CoRo community and verify that the mobile list shows CoRo while retaining the stable ID only for diagnostics.

Written by the indexing model from the issue text.