add cli option --detailed-result-json to print results in JSON

[dilawar]

Close #64. User can now pass --detailed-results-json to print the results in JSON format.

• Adds a dependency serde_json !
• Changes code formatting at a few places because I ran cargo +nightly fmt. I can revert them back. These changes are both harmless and useless.

The prefix Detection result: \n is not printed when --detailed-results-json is used. It is to ensure that if another process captures stdout at a successful run, it can assume it to be a valid JSON.

Example run

Running `/home/dilawar/rxing/target/debug/rxing-cli /home/dilawar/Downloads/3298.png decode --detailed-results-json`
{
  "text": "https://ehr-sample.onrender.com/sample/0003298",
  "rawBytes": [
    104,
    116,
    116,
    112,
    115,
    58,
    47,
    47,
    101,
    104,
    114,
    45,
    115,
    97,
    109,
    112,
    108,
    101,
    46,
    111,
    110,
    114,
    101,
    110,
    100,
    101,
    114,
    46,
    99,
    111,
    109,
    47,
    115,
    97,
    109,
    112,
    108,
    101,
    47,
    48,
    48,
    48,
    51,
    50,
    57,
    56
  ],
  "numBits": 368,
  "resultPoints": [
    {
      "x": 14.202776,
      "y": 14.20277
    },
    {
      "x": 255.11395,
      "y": 14.079432
    },
    {
      "x": 254.94168,
      "y": 254.94171
    },
    {
      "x": 14.079441,
      "y": 255.11395
    }
  ],
  "format": "QR_CODE",
  "resultMetadata": {
    "ERROR_CORRECTION_LEVEL": {
      "ErrorCorrectionLevel": "L"
    },
    "STRUCTURED_APPEND_SEQUENCE": {
      "StructuredAppendSequence": -1
    },
    "SYMBOLOGY_IDENTIFIER": {
      "SymbologyIdentifier": "]Q1"
    },
    "STRUCTURED_APPEND_PARITY": {
      "StructuredAppendParity": -1
    }
  },
  "timestamp": 1750522910447,
  "line_count": 0
}