Remove criterion exclude attribute, use logical criterion combination with not instead

[scymtym]

Before this change, the _exclude attribute in criteria classes led to inconsistent mapping between criterion objects and logic expression objects as well a few complications which arose from handling this mismatch.

This major change in pull request is separated into two commits

1. Introduce the logical criterion combinations with operator not and use it where appropriate.
   As a result of this change, the _exclude attribute is always False.

2. Remove the _exclude and logic for validating and inverting it.

Both commits represent consistent states in which all tests should pass.

[codecov]

Codecov Report

Attention: Patch coverage is 88.88889% with 6 lines in your changes missing coverage. Please review.

Project coverage is 87.61%. Comparing base (4c1ce41) to head (78a0237).
Report is 10 commits behind head on main.

Files with missing lines	Patch %	Lines
...n_engine/omop/criterion/combination/combination.py	44.44%	5 Missing ⚠️
execution_engine/omop/criterion/abstract.py	75.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #242      +/-   ##
==========================================
- Coverage   87.65%   87.61%   -0.04%     
==========================================
  Files          92       92              
  Lines        5897     5887      -10     
==========================================
- Hits         5169     5158      -11     
- Misses        728      729       +1     

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

[glichtner]

super!