CM-22718 - Support scan in batches with progress bar

[MarshalX]

• separate documents by batches
• run many scans in parallel
• fix races with auth token
• remove hardcoded scan_id from the context
• remove hardcoded issue_detected from the context
• add ability to have many scan_id per CLI session
• fix scan_id in async scans (generates on BE side)
• fix report_url
• add support for scan errors (including timeouts) in batching (UI)
  • collect all errors during the scan and don't show until the end
  • show errors in correct --output format!
    • add JSON format support for exceptions. Comment: not required yet
  • raise polling timeout errors
• code refactoring. don't use inner functions if possible (for threads)
• update is_scan_failed logic by issue_detected (we have many issue_detected now)
• add --no-progress-meter flag
• disable progress bar for JSON output
• implement multi-sectioned progress bar
• integrate progress bar to all scans
• move all info logs to debug ones. only progress bar should stay
• remove halo package

Printers:

• rework text printer
  • add support for aggregated scan results
  • change source of scan_id
  • change source of report_url
  • add support for many scan_id per print (UI)
• rework json printer
  • add support for aggregated scan results
  • change source of scan_id
  • change source of report_url
  • ❌ add support for many scan_id per print (UI). Comment: I can't do it without changing JSON structure. I was not allowed to change it
• rework table printer
  • add support for aggregated scan results
  • change source of scan_id
  • change source of report_url
  • add support for many scan_id per print (UI)

[MarshalX]

progress bar demo (fake progress speed):

Screen.Recording.2023-06-30.at.19.04.51.mov

Each batch has its own scan id. This was not standard behavior for CLI. This is how many scan_id were integrated into printers:

• text output:
  
• table output:
  
• JSON is not supported without changing the struct
  

[MarshalX]

Errors displaying. UI synced with Maria. One row means one batch. UUID is scan_id for debug purposes:

[MarshalX]

i place it here for future changes

// The current:
{
    "scan_id": "someUuid",
    "detections": [
        {
            "type": "slack-token",
            "detection_details": {...},
            ...
        }
     ]
}

// The new one. That will support batches
{
    "scan_results" : [
        {
            "scan_id": "someUuid",
            "report_url": "someUrl",
            // it's flexible  and we can add more field here in the future
            "detections": [
                {
                    "type": "slack-token",
                    "detection_details": {...},
                    ...
                }
            ]
        }
    ]

}