Add Guestbook Response Sorting by fields

[stevenwinship]

What this PR does / why we need it: Modern UI needs to sort the output of the get guestbook response api

Which issue(s) this PR closes:#12524

• Closes Update guestbook responses to sort by guestbook response fields #12524

Special notes for your reviewer:

Suggestions on how to test this: create multiple Datasets using a Guestbook and populate responses. Using the API retrieve the responses with various sort/order query parameters. Test with large numbers for performance hits due to the added db table joins.

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

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

Additional documentation:

[coveralls]

coverage: 24.97%. remained the same — 12524-sort-guestbook-responses into develop

[github-actions]

Test Results

403 tests  ±0   388 ✅ ±0   33m 37s ⏱️ +11s
 55 suites ±0    15 💤 ±0 
 55 files   ±0     0 ❌ ±0 

Results for commit fccdd1c. ± Comparison against base commit 0a49c4c.

♻️ This comment has been updated with latest results.

[sonarqubecloud]

Quality Gate failed

Failed conditions
15.7% Coverage on New Code (required ≥ 80%)

See analysis details on SonarQube Cloud

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:12524-sort-guestbook-responses

ghcr.io/gdcc/configbaker:12524-sort-guestbook-responses

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

[qqmyers]

OK _ I see what you're concerned about - not the CriteriaBuilder per se, but the fact that it's a really complex join to sort by dataset name (for example). It sounds like denormalization or a materialized view might be required to be efficient (according to AI). I'm not sure I know enough to decide what the tradeoffs might be there, so maybe some tech hr discussion needed. Alternately - if this looks like more work than expected, perhaps going back to the UI side and asking if sorting on these is really useful versus filtering or allowing guestbook response viewing on a dataset of file page (so one could select a given dataset name and filter by it, with the query underneath just being adding a where dataset_id=X clause (or file, or user, etc.)