Fix agent prosecutor authority access JSON parsing (CIMD-3294 regression)

[allanmckenzie]

Problem

ProsecutingAuthorityProvider.buildFromResponseJson (access-control-sjp-providers) parsed the agentProsecutorAuthorityAccess response field as an array of JsonObjects, each expected to hold a prosecutingAuthority string property:

.map(agentAccess -> agentAccess.getValuesAs(JsonObject.class)
        .stream()
        .map(agent -> agent.getString("prosecutingAuthority"))
        .collect(Collectors.toList()))

But agentProsecutorAuthorityAccess is an array of strings. At runtime this throws:

java.lang.ClassCastException: org.eclipse.parsson.JsonStringImpl cannot be cast to jakarta.json.JsonObject

for any user with agent prosecutor access. It surfaced as HTTP 500s on cpp-context-mi-reportdata's SJP resulted-cases-count and case-export endpoints during the Java 25 / WildFly 40 upgrade (CasesCountIT.shouldVerifyResultedCasesCountMultipleAgents, CaseExportInJsonFormatExtractIT).

Where this code came from / root cause

The original, correct CIMD-3294 implementation on release/17.104.x-DD-41592 parsed the field as strings:

.map(arr -> arr.getValuesAs(JsonString.class)
        .stream()
        .map(JsonString::getString)
        .collect(Collectors.toList()))

When the feature was recreated on the 25.104.x line in commit 5f6e0925 ("Restore agent prosecutor authority access (CIMD-3294)"), the parsing was reimplemented with the wrong element type (JsonObject instead of JsonString) and no test was added for the agent-access path, so the regression shipped in 25.104.0-M7 unnoticed.

Fix

• Restore the string-array parsing (getValuesAs(JsonString.class) + JsonString::getString) from release/17.104.x-DD-41592.
• Add ProsecutingAuthorityProviderTest coverage: parse the string array into the access list, and grant access via an agent prosecutor authority. (Reproduces the CCE with the old code; green with the fix.)
• Bump hearing.version 17.104.168 → 17.104.176 in the root pom to satisfy enforce-moj-latest-interfaces (latest released hearing-query-api RAML).

Verification

• Full cpp-platform-libraries reactor build green (enforcer on); ProsecutingAuthorityProviderTest 11/11, jacoco coverage met.
• Proven end-to-end against mi-reportdata: patched only this class into the deployed WAR and re-ran the affected ITs — CaseExportInJsonFormatExtractIT 2/2 and CasesCountIT 5/5 (incl. …MultipleAgents) now pass.

🤖 Generated with Claude Code