getVersionFileCounts API endpoints extended to support filtering by criteria

[GPortas]

What this PR does / why we need it:

Extended the getVersionFileCounts endpoint (/api/datasets/{id}/versions/{versionId}/files/counts) to support filtering by criteria.

In particular, the endpoint now accepts the following optional criteria query parameters:

• contentType
• accessStatus
• categoryName
• tabularTagName
• searchText

This filtering criteria is the same as the one for the getVersionFiles endpoint.

Which issue(s) this PR closes:

• Closes [Spike - API] Extend the file counts endpoint to return counts based on selected filters and search criteria #9907

Special notes for your reviewer:

IT case added for each of the supported query parameters, so a very extensive manual test is not necessary.

DatasetVersionFilesServiceBean has been refactored to make the filtering criteria logic reusable for multiple endpoints.

Suggestions on how to test this:

Create a dataset and upload files. Once you have uploaded the files, call the endpoint with the new criteria parameters to test that the returned counts are correct.

Example for content type:

curl http://localhost:8080/api/datasets/2/versions/:latest/files/counts?contentType=image/png
If the dataset is not public, you will need to add the API key to the call.

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

No

Is there a release notes update needed for this change?:

Yes

Additional documentation:

N/A

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:9907-file-counts-with-criteria

ghcr.io/gdcc/configbaker:9907-file-counts-with-criteria

🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name.

[kcondon]

@GPortas
Issues found:

1. Not able to operate on deaccessioned dataset, says version not found. Owner/editor should be able to, not others.
2. API endpoint without contentType arg seems to wait on command prompt until hit return again. Doesn't work that way with contentType. More of a curiosity but seems like something not quite right.

[GPortas]

@kcondon

Thank you for your feedback.

1. Support for deaccessioned datasets is included in the other PR, this one doesn't contain those changes, but it should work as you describe when merging.

2. I think something weird is going on with double quotes. Can you try with these examples?

curl http://localhost:8080/api/datasets/<DATASED_ID>/versions/:latest/files/counts
curl http://localhost:8080/api/datasets/<DATASED_ID>/versions/:latest/files/counts?contentType=image/png

These calls are working for me.

[kcondon]

@GPortas Thanks. Yes, I'd run into the quotes thing in some way with Jim. Exchanging single quotes for double some times works: curl 'http://localhost:8080/api/datasets/:persistentId/versions/:latest/nts?persistentId=doi:10.70122/FK2/IHEHUV&contentType=text/tab-separated-values'
{"status":"OK","data":{"total":1,"perContentType":{"text/tab-separated-values":1},"perCategoryName":{},"perTabularTagName":{},"perAccessStatus":{"Public":1}}}

I thought I'd tried that here already but it must have been the other pr. OK, will merge, seeing that deaccession is addressed in the other pr but note there is a permissions issue around the endpoint in the other pr for deaccessioned datasets.