Configure data explorer response views

[eviltester]

Summary

• Add Thingifier GUI configuration for Data Explorer response views.
• Project Data Explorer list/detail/relationship output through configured public views.
• Keep entity definitions decoupled from UI/default response-view concerns.

Validation

• mvn -q -pl ercoremodel,thingifier test
• mvn -q -pl challenger "-Dtest=ShoppingCartApiTest,ShoppingCartDefaultGuiTest,ShoppingCartModelTest" test

[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: b7c76762ef

ℹ️ 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]

Reject unknown response views instead of exposing every field

When a configured view name is misspelled, renamed, or registered against the wrong entity, this filter silently converts the configuration to null; DefaultGuiHtmlPages.isResponseFieldVisible and the JSON/XML converters interpret null as no projection and render every field. A typo in a view intended to hide tokens or other internal data therefore fails open in the Data Explorer rather than producing a configuration error or an empty projection.

Useful? React with 👍 / 👎.