Add route after-response callbacks

[eviltester]

Closes #174

Summary

• Add route-level afterResponse callbacks that run after final response rendering and before legacy/global HTTP response hooks.
• Expose the final status, headers, content type, optional body, public route, resolved target entity/identifier, principal, and data scope to observational callbacks.
• Log and preserve the already-produced response when an after-response callback throws.
• Attach source and Javadoc jars during normal Maven package/install builds.

Verification

• Full Maven verification passed via the commit hook across all modules.
• mvn -q clean install also passed locally and installed the updated snapshot, sources, and Javadocs to Maven local.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5937418cad

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Return a read-only structured response snapshot

When an observational callback calls response.apiResponse().withStatusCode(...), setBody(...), or clearBody(), it mutates the same ApiResponse referenced by the returned HttpApiResponse; that class delegates status and body rendering to this object. The callback can therefore alter the caller-visible response despite this API being documented as immutable/read-only and preserving the already-rendered response. Expose a defensive/read-only representation instead of the mutable underlying object.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Apply callbacks to the legacy query response path

When callers use the public query(HttpApiRequest, String) helper instead of queryRequest, execution never reaches this callback phase: that helper renders its GET response and returns directly through the legacy response hooks. Consequently, an afterResponse callback registered on the queried GET route silently does not run depending on which public HTTP entry point is used. Route this helper through the common response pipeline or explicitly invoke the new callback phase there.

Useful? React with 👍 / 👎.