fix bug Status Operation control report isn't correct

Summary: В репорте Control operation не правильный статус

Envornment:
http://172.16.101.100:3000/
Linux
Firefox

Precondition:
Пользователь авторизован
Открыта страница "Dashboard" (http://172.16.101.100:3000/dashboard)
Открыта вкладка "Reports"

Steps to reproduce:
1. Выбрать дату 07.08.2023
2. В списке репортов открыть репорт # 25736
3. Посмотреть видео репорта # 25736
4. Посмотреть снепшоты репорта # 25736

Expected result:
В репорте статус "Compliance"

Actual result:
В репорте статус "Violation"

Видео со снепшотами: https://drive.google.com/file/d/1vSJyC3Gf2RUYnPqocf7GU1HH-7AEwEaY/view?usp=drive_link

Скаченные видео:
https://drive.google.com/file/d/1KgBaIKO1ev4wyxQq_r2Eq17kTGEcmUqs/view?usp=drive_link
https://drive.google.com/file/d/16SqwZyJeH_fP_ekpE-LYBMB5VCgbUx-U/view?usp=drive_link

The issue describes a status mismatch in a control operation report on a dashboard. The report #25736 shows 'Violation' instead of 'Compliance' for date 07.08.2023. Start by examining the report generation logic, likely in the backend API, and the frontend components that display report status. Check the data source and status mapping. The provided Google Drive links contain videos and snapshots for visual reference. Determine what defines 'Compliance' vs. 'Violation' and why the mismatch occurs.

Written by the indexing model from the issue text.