Return metadata on executed Update

[Qup42]

SPARQL Update requests sent via HTTP are now answered with a JSON object that contains useful metadata about the request, for example the number of changed triples and timing statistics.

[codecov]

Codecov Report

Attention: Patch coverage is 79.62963% with 22 lines in your changes missing coverage. Please review.

Project coverage is 89.89%. Comparing base (d7ec9be) to head (bdf45a7).
Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
src/engine/Server.cpp	78.12%	14 Missing ⚠️
src/index/DeltaTriples.cpp	75.00%	8 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1675      +/-   ##
==========================================
- Coverage   89.90%   89.89%   -0.01%     
==========================================
  Files         393      393              
  Lines       37479    37565      +86     
  Branches     4221     4222       +1     
==========================================
+ Hits        33694    33770      +76     
- Misses       2482     2494      +12     
+ Partials     1303     1301       -2     

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

[joka921]

This looks very nice, I only have minor suggestions.
We'll have to try this out to check the format.

[joka921]

The code looks very clean now, only some miinor suggestions remain.
And @hannahbast could try it out to see if the response fits her expectations.

[joka921]

Thank you very much! I have some minor suggestions + 1.5 questions.

[joka921]

This looks very great now, did @hannahbast sign off on the exact format in the meantime?
The only thing that remains is fixing the test failure (you changed a error message text, which is asserted).

[Qup42]

Yes we discussed it yesterday evening and Hannah approved. I didn't get to adjusting the tests between the changes in the meeting and now, but will do that in the next 3 hours.
This area still has the topics of returning the metadata in the format request with Accept, but I want to do a little research how other engines do this before inventing something new. The time breakdown doesn't currently add up (time is lost). Nothing jumped at me so fixing this is postponed, because this already provides significant value as-is and blocks some other PRs. (See the Issues in the GitHub Project for more detailed Info.)

[sparql-conformance]

Conformance check passed ✅

No test result changes.

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

[sonarqubecloud]

Quality Gate passed

Issues
2 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