[veto9292]

Supersedes #2325 — this branch contains all of its commits plus the logging
system rebuild, so the two are reviewed and merged together.

Logging system rebuild

Logging kept three separate records of what the app did: the engine held one in
memory, the logs page held another, and a file held a third, each with different
contents and different rules. None held the whole picture, and the page could
only ever show the engine's half.

It ran on loggy, which was suspected of freezing the app during heavy
logging. Measurement cleared loggy — the real cost was print() at 82-133ms per
2000 lines against 11-20ms for everything else — but it was replaced with
package:logging regardless: maintained by the Dart team, a Flutter Favorite,
and it separates producing a record from deciding where it goes.

Before	After
Three separate records, none complete	One stream, four independent listeners
Page showed engine logs only, starting empty each time	Page shows every source, with history already there
No search or filter	Filter by source, severity and text
Two share buttons, desktop only	One sheet, every platform
Two logging controls in Settings that could contradict	One control, on the logs page
Log file wiped at every launch	Kept across runs, errors only
Two vocabularies for the same levels	One: trace, debug, info, warn, error

Bugs fixed

Cost us crash evidence:

• Crash reports arrived as one line with no stack — assigning FlutterError.onError
  replaced presentError, discarding Flutter's own report
• The log file was erased at every launch, losing exactly what preceded a crash
• Engine logs stopped permanently after any stream error: the re-arm sat behind
  if (!isSingleChannel()), which is false on desktop, and listenSingle drops a
  subscription for good when its stream errors
• Trimming the log file wrote blocks of NUL bytes into it — IOSink.close() is
  asynchronous and the trim did not await it
• Connection failures were logged at info, so they never reached the file

Wrong or misleading:

• Saving a shared file reported success without writing anything: on desktop
  FilePicker.saveFile only returns a path, and its bytes argument throws on macOS
• The file offered as a "hang report" was a startup snapshot; the real crash file
  is what the Go runtime writes via debug.SetCrashOutput
• The engine log pointed at an always-empty path; the real file is data/box.log
• Debug mode and log level could disagree — the core already derives one from the
  other in buildconfighelper.go
• Phones could not share logs at all, and TRACE fell through to the INFO default
• No text field in a debug build accepted keyboard input: enableFlutterDriverExtension
  installs a TestTextInput that takes over the platform text channel. It is now
  behind --dart-define=driver=true

Notes

• Deleted: log_parser, log_entity, log_repository, log_failure,
  logger_controller, analytics_logger, the engine's private 300-message buffer,
  and the Debug mode switch
• Nothing constructs a Logger directly; the mixins and factories in
  custom_loggers.dart are the only way to get one
• All 11 locales updated
• The Core crash entry stays hidden until hiddify-core is rebuilt: the
  crash-report mechanism is newer than the currently released binary

Also included, from #2325

Profile management, sorting and update-status improvements, localization,
connection haptics, native iOS swipe-back, and the hiddify-core bump to db74dfc.

CI

The three failing jobs fail identically on #2325 and are unrelated to this work:

• Windows — MSIX packaging needs windows/sign.pfx, written from
  secrets.WINDOWS_SIGNING_KEY, which GitHub does not expose to fork pull
  requests. The .exe itself builds
• Android (apk, aab) — Kotlin fails against the prebuilt core AAR that
  make android-libs downloads from the hiddify-core releases. The Kotlin glue
  expects androidPackageName, closeNeighborMonitor and dnsServerAddress.value,
  which that published build predates

Linux, macOS and the test job pass.