`jf docker scan --fail=true` does not actually fail

Describe the bug

When scanning a Docker Image in a Jenkins job, using the CLI-plugin, we execute the following command:
jf 'docker scan <DOCKER_IMAGE> --fail=true --watches=<SPECIFIC_WATCH>'

The output lists show a fine list of Security Violations that should trigger the exit code to return as 3.

Current behavior

Running the "jf docker scan"-command produces a success, not a fail with an exit code of 3

The job run with debug output:

docker_scan_does_not_fail-DEBUG.txt

Reproduction steps

Executing the below stage does not fail as expected

    stage('Jfrog CLI') {
        withEnv([
            "JFROG_BINARY_PATH=${tool 'jfrog-cli'}",
            "JFROG_CLI_HOME_DIR=${env.WORKSPACE_TMP}/jfrog/${env.BUILD_NUMBER}/.jfrog",
            "JFROG_CLI_LOG_LEVEL=DEBUG",
            "PATH+=${tool 'jfrog-cli'}"
            ]) {
            try {
                jf 'docker scan <DOCKER_IMAGE> --fail=true --watches=<FAIL_Critical_All_Resources>'
            } catch (error) {
                currentBuild.result = 'FAILURE'
            }
        }
    }

Expected behavior

Something like this at the end of the stage

and the build marked as FAILURE

JFrog CLI-Core version

I do not know which version is correct here.
The JFrog Jenkins plugin is version 1.5.8

JFrog CLI version (if applicable)

2.74.0

Operating system type and version

Debian Linux (Jenkins inbound-agent docker image)

JFrog Artifactory version

7.49.6

JFrog Xray version

3.107.21

Start by reproducing jf docker scan <DOCKER_IMAGE> --fail=true --watches=<SPECIFIC_WATCH> with CLI version 2.74.0 and the supplied debug output, then trace why security violations do not produce exit code 3. Done means the command returns exit code 3 and the Jenkins stage is marked FAILURE when the scan finds violations.