feat: add cipherSuites option and "unsafe" fingerprint to TLS UI settings

[Copilot]

Adds two missing TLS options from the XTLS TLS spec to the server configuration UI.

Changes

• arrays.xml — Added unsafe to the streamsecurity_utls fingerprint list
• ProfileItem.kt — Added cipherSuites: String? field
• layout_tls.xml — Added EditText for cipher suites (between ALPN and allowInsecure)
• strings.xml — Added label string server_lab_cipher_suites
• ServerActivity.kt — Field binding, visibility control (shown for TLS, hidden for REALITY/none), load/save
• CoreOutboundBuilder.kt — Passes cipherSuites to TlsSettingsBean

The cipherSuites field in TlsSettingsBean already existed but was never wired to the UI or ProfileItem.

[patterniha]

@copilot

check everything is ok and you haven't missed anything.

[Copilot]

@copilot

check everything is ok and you haven't missed anything.

I've verified the implementation is complete:

1. ProfileItem.kt — cipherSuites: String? field added ✅
2. layout_tls.xml — EditText with proper focus chain (ALPN → cipherSuites → allowInsecure) ✅
3. strings.xml — Label string added ✅
4. ServerActivity.kt — Field binding, load/save, visibility (shown for TLS, hidden for REALITY/none) ✅
5. CoreOutboundBuilder.kt — Passes value to TlsSettingsBean using .nullIfBlank() ✅
6. arrays.xml — unsafe fingerprint added ✅

No issues found:

• No database migration needed — MMKV uses JSON serialization, and the new nullable field deserializes as null for existing entries.
• No share link format change needed — cipherSuites has no standard URI query parameter in the V2Ray/XTLS share link spec, matching how other local-only TLS fields are handled.
• The TlsSettingsBean already had the cipherSuites field defined, so it's fully compatible.