ux+fix: rename Network Identity → Device Address (UI) + redundancy authors

#6: UI rename — Network Identity → Device Address.
Just labels/wording, no backend changes. Tauri command names
(list_identities, create_identity, etc.) and DTO fields stay as-is;
the rename is purely user-facing. Settings labels, lightbox titles,
toasts, danger-zone text, and welcome-screen "Import an Identity"
button all updated. Distinguishes more clearly from Personas (which
ARE the posting identity peers see).

#7: Bug fix — redundancy showed 0 for new posts.
Root cause: get_redundancy_summary queried
  SELECT p.id FROM posts WHERE p.author = ?1
with ?1 = self.node_id (the device's network NodeId). After the
v0.6.0 network/posting-ID split, posts are authored by posting
identities (personas), not the network NodeId — so the query
returned 0 of my posts and the redundancy panel showed all zeros.

Fix: storage::get_redundancy_summary now takes &[NodeId] and uses
WHERE author IN (?, ?, ...) over every persona on the device.
Node::get_redundancy_summary gathers them via
list_posting_identities() before delegating.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

crates/core/src/node.rs

@@ -3442,7 +3442,12 @@ impl Node {
 
     pub async fn get_redundancy_summary(&self) -> anyhow::Result<(usize, usize, usize, usize)> {
         let storage = self.storage.get().await;
-        storage.get_redundancy_summary(&self.node_id, 3_600_000)
+        // Posts are authored by posting identities (personas), not the
+        // network NodeId. Use every persona on this device so the
+        // summary counts all of my posts across personas.
+        let author_ids: Vec<NodeId> = storage.list_posting_identities()?
+            .into_iter().map(|p| p.node_id).collect();
+        storage.get_redundancy_summary(&author_ids, 3_600_000)
     }
 
     // ---- Networking ----