Add key range parameters to REST API v2

[dimas-b]

• In "diff" API

• In "get entries"

• New "get contents" endpoint for range queries

This is just an API-level change to reserve REST paths and query
parameters. Server-side implementation to be done separately.

Closes #5591

[codecov]

Codecov Report

Base: 83.91% // Head: 79.26% // Decreases project coverage by -4.64% ⚠️

Coverage data is based on head (4b17846) compared to base (09962ca).
Patch coverage: 32.65% of modified lines in pull request are covered.

❗ Current head 4b17846 differs from pull request most recent head 60f7dc3. Consider uploading reports for the commit 60f7dc3 to get more accurate results

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #5656      +/-   ##
============================================
- Coverage     83.91%   79.26%   -4.65%     
- Complexity        0     3724    +3724     
============================================
  Files            30      536     +506     
  Lines          1473    16515   +15042     
  Branches        238     1613    +1375     
============================================
+ Hits           1236    13090   +11854     
- Misses          171     2804    +2633     
- Partials         66      621     +555     

Flag	Coverage Δ
java	78.71% <32.65%> (?)
javascript	82.91% <ø> (?)
python	83.91% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
...a/org/projectnessie/client/api/GetDiffBuilder.java	0.00% <ø> (ø)
...g/projectnessie/client/http/v2api/HttpGetDiff.java	0.00% <0.00%> (ø)
...ava/org/projectnessie/api/v2/http/HttpTreeApi.java	0.00% <0.00%> (ø)
...va/org/projectnessie/api/v2/params/DiffParams.java	0.00% <0.00%> (ø)
...ctnessie/error/NessieContentNotFoundException.java	42.85% <0.00%> (ø)
...ain/java/org/projectnessie/model/DiffResponse.java	0.00% <ø> (ø)
...g/projectnessie/client/http/v1api/HttpGetDiff.java	29.41% <23.07%> (ø)
...ojectnessie/client/builder/BaseGetDiffBuilder.java	15.78% <27.27%> (ø)
...rg/projectnessie/api/v2/params/AbstractParams.java	58.33% <100.00%> (ø)
...org/projectnessie/api/v2/params/EntriesParams.java	87.50% <100.00%> (ø)
... and 506 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[dimas-b]

@snazy : do you want range params for reference endpoints too?

[snazy]

@snazy : do you want range params for reference endpoints too?

Yes, that would be good. It would also be nicer to the new storage stuff to change the maxKey parameter from exclusive to _inclusive. We can technically encode a prefix-query with the min and max parameters:

• from...to : minKey defines the start (inclusive) and maxKey the end (inclusive)
• from : minKey defines the start (inclusive)
• to : maxKey defines the end (inclusive)
• prefix : minKey == maxKey define the prefix for the returned keys. "min equal to max" doesn't really make sense for a query and should be performed via a point-query (get-content) - so we could abuse this case. From a usability perspective if would probably make sense to have a separate parameter for this though.

[snazy]

@snazy : do you want range params for reference endpoints too?

It could make sense to have this kind of query for references, so yes - especially the prefix one.

[snazy]

Shall we continue on this one?
We can omit New "get contents" endpoint for range queries for now, but have range-queries for getAllReferences

[snazy]

Closing with its successor #6743