Intersection violation print message to stand out more

[eytanadler]

Purpose

New intersection violation message that is easier to notice in the output.

Expected time until merged

Type of change

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (non-backwards-compatible fix or feature)
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Documentation update
• Maintenance update
• Other (please describe)

Testing

Checklist

• I have run flake8 and black to make sure the Python code adheres to PEP-8 and is consistently formatted
• I have formatted the Fortran code with fprettify or C/C++ code with clang-format as applicable
• I have run unit and regression tests which pass locally with my changes
• I have added new tests that prove my fix is effective or that my feature works
• I have added necessary documentation

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.46%. Comparing base (9caea1a) to head (3809e2f).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #240   +/-   ##
=======================================
  Coverage   65.46%   65.46%           
=======================================
  Files          47       47           
  Lines       12265    12265           
=======================================
  Hits         8029     8029           
  Misses       4236     4236           

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

[hajdik]

Stands out in the output, LGTM