Warn when parsed PRT errors are inconsistent

[berland]

Issue
Resolves #8650

Approach
Short description of the approach

(Screenshot of new behavior in GUI if applicable)

• PR title captures the intent of the changes, and is fitting for release notes.
• Added appropriate release note label
• Commit history is consistent and clean, in line with the contribution guidelines.
• Make sure unit tests pass locally after every commit (git rebase -i main --exec 'pytest tests/unit_tests -n logical -m "not integration_test"')

When applicable

• When there are user facing changes: Updated documentation
• New behavior or changes to existing untested code: Ensured that unit tests are added (See Ground Rules).
• Large PR: Prepare changes in small commits for more convenient review
• Bug fix: Add regression test for the bug
• Bug fix: Create Backport PR to latest release

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.45%. Comparing base (a44408b) to head (21bae8c).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8773      +/-   ##
==========================================
+ Coverage   91.40%   91.45%   +0.05%     
==========================================
  Files         343      343              
  Lines       21269    21269              
==========================================
+ Hits        19441    19452      +11     
+ Misses       1828     1817      -11     

Flag	Coverage Δ
cli-tests	38.93% <ø> (+0.17%)	⬆️
gui-tests	72.41% <ø> (ø)
performance-tests	49.27% <ø> (ø)
unit-tests	80.14% <ø> (+0.02%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[eivindjahren]

👍