fix(persona): create-persona does nothing on a State-A account

[stormer78]

Symptom

In the Create Persona DID overlay, pressing Enter after typing a label did nothing — no progress, no error, no DID. (Reported right after #134 merged.)

Root cause

A State-A account — bootstrapped (VTA + context) but with no persona/community yet — runs run_degraded_loop, not the main runtime loop. That's exactly when you'd create your first persona DID.

The overlay's open and label-edit actions go through the shared handle_nav_action reducer, so they worked (the typed name appeared). But CreatePersonaSubmit / CreatePersonaCopy are loop-local and were only wired into the runtime loop — the degraded loop's catch-all _ => {} silently dropped them.

Fix

Wire both arms into run_degraded_loop, minting via the join context's admin VTA + config (minting needs only the admin session + account context, both present in State-A — ctx.profile == self.profile, so run_create_persona's persist path is correct).

Also documented the dual-loop contract in the nav_reducer_defers_loop_local_arms test so the next loop-local action isn't dropped the same way.

Verification

• cargo build, cargo clippy --all-targets, and cargo test -p openvtc (160 passed) all clean.
• Not driven against a live VTA from CI; verified by build/tests + root-cause analysis. Manual check after merge: fresh account → menu "Create Persona DID" → type a label → Enter → progress then the DID.

Follow-up (not in this PR): the runtime and degraded loops duplicate several loop-local arms (StartJoin, DeleteCommunity, now CreatePersona) — a shared loop-local dispatcher would prevent this whole class of "handled in one loop, dropped in the other" bug.