[Loukious]

The upload parser expects a response format OnlineHashCrack no longer
uses, so successful uploads are reported as failures.

From the app's debug log DB on a test device, a real upload response:

{"notice":"...","next_steps":"Results are available in your
OnlineHashCrack dashboard: https://onlinehashcrack.com/tasks",
"accepted":{"count":1,"hashes":["WPA*02*..."]},
"skipped":{"count":0,"reason":"already_sent","hashes":[]},
"rejected":{"count":0,"hashes":[]}}

The upload itself succeeded (accepted count 1, the hash landed in the
user's OHC dashboard) — but parseUploadResult() only recognizes the
legacy {"success":true,"message":...} shape. It matched nothing, fell
through every branch, and the app toasted a generic upload-failed
message with no detail.

Recognize the current format in the JSON branch:

• accepted.count > 0 -> SUCCESS
• skipped.count > 0 -> ALREADY (with the skip reason, e.g. already_sent)
• otherwise -> FAILED with the rejected reason

The legacy success-flag path is kept for older/other response shapes,
and the non-JSON text fallbacks (already/success/uploaded keywords)
are unchanged.