jf scan regression issue since jfrog-cli v.2.86.0

Describe the bug

We use "jf scan" with "--extended-table" and "--watches" options to scan a tar file of a Docker image.

Up to jfrog-cli v2.85.0 (jfrog-security-cli v1.23.0). Since jfrog-cli v2.86.0 (jfrog-security-cli v1.24.0) this fails.

Current behavior

> jf scan --extended-table --watches=foobar-min-severity-critical --fail=false /tmp/tmp.BKBGlj/image.tar
[Info] JFrog Xray Indexer 3.111.20 is not cached locally. Downloading it now...
[Info] The downloaded Xray Indexer version is 3.111.20
[Info] Xray is processing your scan results...
[Info] No violations found.
[Info] Trace ID for JFrog Platform logs: 123456789
[Error] failed to record results: ParseNewTargetResults must be called before starting to parse issues

Reproduction steps

No response

Expected behavior

jf scan should finish without error

JFrog CLI version

2.86.0 or newer

Operating system type and version

Docker / Ubuntu 24..04

JFrog Artifactory version

No response

JFrog Xray version

No response

Start with the jf scan path handling --extended-table and --watches, and compare behavior between jfrog-cli 2.85.0 and 2.86.0 using the tar-file command shown. Confirm the regression and trace the result parsing sequence; done means the scan finishes without the “ParseNewTargetResults” error.