'API inconsistency for release time between JsonParser and JsonPrinter

[stevenwinship]

What this PR does / why we need it: The output of JsonPrinter includes "releaseTime" where the input to JsonParser only accepted "releaseDate"

Which issue(s) this PR closes:#11594

• Closes API inconsistency for release time between JsonParser/JsonPrinter #11594

Special notes for your reviewer:

Suggestions on how to test this:

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 is 24.976% — 11594-release-time-inconsistency-api into develop. No base build found for develop.

[rtreacy]

Claude
Overall this is a small, well-targeted, backward-compatible fix with adequate test coverage.
Two minor findings (neither blocking):

1. The new test shadows the class field sut (the actual JsonParser under test) with an unrelated local String sut = "foobar", and redundantly re-instantiates a parser/mocks instead of reusing the existing sut field from @beforeeach — just a readability/duplication nit.
2. The release note has two typos ("preferance" → "preference", "continue to truncated" → "continue to be truncated").

[github-actions]

📦 Pushed preview images as

ghcr.io/gdcc/dataverse:11594-release-time-inconsistency-api

ghcr.io/gdcc/configbaker:11594-release-time-inconsistency-api

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