Add Clang 15 C++17 build with error tolerance

[lucaam]

This PR adds Clang 15 to the build matrix C++17 support and set it as non-voting (continue-on-error: true) and use the -k option to cmake continue going even if error occurs.

[joka921]

This can be the first step towards such a CI check.
I think for this to be very useful, we need also a postprocessor that reads the error output of the compilation, and lists the failing and non-failing .cpp fiiles that can and can't be compiled.
This can then be combined with an explicit whitelist (Files that we have already fixed) to really check, that we don't regress, and that we correctly track our progress.
But I assume, that this is your initial step, and as you get the output of the CI pipeline you can used that to develop the further tools.

Let me know if I can be of assistance.

[joka921]

As long as this compilation doesn't work in fact, I would prefer having an additional
variable to be used here, such that this reads if (COMPILER_VERSION LESS 16 && !COMPILER_VERSION_CHECK_DEACTIVATED

[lucaam]

Sure, way better solution, gonna push it soon

[joka921]

I have just started the pipeline, this would be an initial step to track the progress.

[sparql-conformance]

Conformance check passed ✅

No test result changes.

Details: https://qlever.cs.uni-freiburg.de/sparql-conformance-ui?cur=c7faf132c17840e830772cf6b1d64c9910f49889&prev=098b79c715f9992972a8d3452f5bd10e303c6ce4

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.00%. Comparing base (db6825c) to head (c7faf13).
Report is 5 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1764      +/-   ##
==========================================
+ Coverage   89.98%   90.00%   +0.01%     
==========================================
  Files         395      395              
  Lines       37693    37793     +100     
  Branches     4241     4257      +16     
==========================================
+ Hits        33919    34016      +97     
- Misses       2478     2479       +1     
- Partials     1296     1298       +2     

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

[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

[lucaam]

This can be the first step towards such a CI check. I think for this to be very useful, we need also a postprocessor that reads the error output of the compilation, and lists the failing and non-failing .cpp fiiles that can and can't be compiled. This can then be combined with an explicit whitelist (Files that we have already fixed) to really check, that we don't regress, and that we correctly track our progress. But I assume, that this is your initial step, and as you get the output of the CI pipeline you can used that to develop the further tools.

Let me know if I can be of assistance.

I think we could think about it in the future. Would you be open to a Python-based solution for this (we could include in a Github Workflow)?