Add json option for advance reports

[AShivangi]

Problem solved by the commit

• CR-1217445 [xrt-smi] verbosity enabled when a single test is run
• CR-1217447 [xrt-smi] remove xclbin path/dpu seq path from validate verbose
• add --json option to advanced reports

Bug / issue (if any) fixed, which PR introduced the bug, how it was discovered

How problem was solved, alternative solutions (if any) and why they were rejected

• removed the if statement which checks if a single test is run
• remove xclbin path/dpu seq and kernel name from validate
• add a json option

Risks (if any) associated the changes in the commit

Low

What has been tested and how, request additional testing if necessary

Tested on stx/mcdm:

>xrt-smi advanced --report clocks --json
{
    "clocks": [
        {
            "id": "H Clock",
            "description": "System",
            "freq_mhz": "800"
        },
        {
            "id": "MP-NPU Clock",
            "description": "System",
            "freq_mhz": "400"
        }
    ]
}

>xrt-smi advanced --report clocks
Clocks
  H Clock                : 800 MHz
  MP-NPU Clock           : 400 MHz

>xrt-smi advanced --report preemption
Premption Telemetry Data
 No hardware contexts running on device

>xrt-smi advanced --report preemption --json
Premption Telemetry Data
 No hardware contexts running on device

>xrt-smi advanced --report preemption
Premption Telemetry Data
  |User Task  ||Ctx ID  ||Set Hints  ||Unset Hints  ||Checkpoint Events  ||Frame Boundary Events  |
  |-----------||--------||-----------||-------------||-------------------||-----------------------|
  |0          ||1       ||N/A        ||N/A          ||N/A                ||N/A                    |

>xrt-smi advanced --report preemption --json
{
    "telemetry": [
        {
            "user_task": "0",
            "slot_index": "1",
            "preemption_flag_set": "N\/A",
            "preemption_flag_unset": "N\/A",
            "preemption_checkpoint_event": "N\/A",
            "preemption_frame_boundary_events": "N\/A"
        }
    ]
}

Documentation impact (if any)

N/A