[AWG/WARP] Edit profiles and number generated names

[Regstar2]

Summary

Follow-up to #84.

• allow editing the profile name and the full saved AWG/WARP .conf for both imported and automatically provisioned profiles;
• validate changed config text with the existing Kotlin parser and native AWG validation before replacing the saved config;
• preserve health for name-only edits, but reset changed configs to Not checked;
• clear stored generated public-key metadata if the edited config changes PrivateKey;
• default newly generated Consumer WARP profiles to WARP 1, WARP 2, … based on existing numbered profiles;
• harden AWG/WARP health/autotune so a candidate must receive a real Telegram MTProto resPQ response to req_pq_multi, preventing generic-WARP false positives with zero Telegram downstream;
• keep all new UI text localized in Russian and English;
• update README/CHANGELOG and add unit coverage for generated-name sequencing.

Scope

The native AWG/WARP transport and AwgWarpDialer are not changed.

Manual checks

After CI:

1. Create two automatic profiles and verify default names increment.
2. Open an automatic profile, rename it only, save, and verify its health status is preserved.
3. Edit a safe AWG parameter (for example Jc), save, and verify status becomes Not checked.
4. Run Check profile on the previously problematic profile; it must no longer pass if Telegram MTProto downstream is silent (telegram_roundtrip_failed).
5. Generate/check a replacement profile and verify Telegram traffic has real downstream bytes.
6. Repeat rename/config editing for an imported profile.
7. Verify editing is disabled while the proxy is running.
8. Check both Russian and English UI.