c++17 concepts with CPP_template for engine/*.{cpp,h} files

[sebastian-wieczorek]

Backport C++20 concepts in the src/engine subdirecotory to C++17 using macros from range-v3.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.11%. Comparing base (a9f6895) to head (c33b909).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1812      +/-   ##
==========================================
- Coverage   90.12%   90.11%   -0.01%     
==========================================
  Files         399      399              
  Lines       38199    38201       +2     
  Branches     4281     4281              
==========================================
- Hits        34426    34424       -2     
- Misses       2473     2479       +6     
+ Partials     1300     1298       -2     

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

[joka921]

Thank you very much,
I have made some small remarks for myself which I will quickly address and then we can merge this. There remains no further work here for you @sebastian-wieczorek

[joka921]

@sebastian-wieczorek
Please do not force-push your branch after the initial review.

1. You destroy the change diff for incremental reviews.
2. You force-override any changes that I have made on your branch since your last push, especially since I explicitly stated that I do those quick fixes and can then directly merge it again. Now I have to look over everything again, and we have to wait for the CI

[sparql-conformance]

Conformance check passed ✅

No test result changes.

Details: https://qlever.cs.uni-freiburg.de/sparql-conformance-ui?cur=c33b909d36ff52194e77ab5d5c7f528b39b46c31&prev=a9f68959ac4bc115dbd77e2f953a3da24b6307d4

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[sebastian-wieczorek]

1. diff for incremental reviews.
2. You force-override any changes that I have made on your branch since your last push, especially since I explicitly stated that I do those quick fixes and can then directly merge it again. Now I have to look over everything again, and we have to wait for the CI

should I restore it? I thought this comment says I need to fix it but you did it, sorry for the confusion.