Support distinct jsonviews for serialization and deserialization

[Postremus]

Before, the jsonview for the request body could leak affect the serialization side, and cause the response entity to be written with the wrong jsonview. Now, the method and class level jsonview affect the serialization side, while a method parameter jsonview affect only the deserialization side.

However, technically speaking, this is also a minor breaking change for undocumented behaviour. Should be worth it though, since this implementation is less surprising, and follows what is currently documented at https://quarkus.io/version/main/guides/rest#jsonview-support.

Therefore, a note for the migration guide:

closes #46751

---

Quarkus Rest - JsonView Deserialization changes

With this version, the deserialization support for jsonviews gets documented and slightly changed.

For example:

(1)

@POST
@Produces(MediaType.APPLICATION_JSON)
@Consumes(MediaType.APPLICATION_JSON)
@JsonView(Views.Private.class)
public RestResponse<User> create(User user) {
    return RestResponse.status(CREATED, user);
}

(2)
@POST
@Produces(MediaType.APPLICATION_JSON)
@Consumes(MediaType.APPLICATION_JSON)
@JsonView(Views.Private.class)
public RestResponse<User> create(@JsonView(Views.Public.class) User user) {
    return RestResponse.status(CREATED, user);
}

(1) The method parameter user was also deserialized using the Views.Private view.
(2) The method parameter user was most likely to correctly use the expected Views.Public view for deserialization. For Serialization however, the Views.Public was also used, although the method is annoted with the Views.Private view.

The behaviour changed, so that now the deserialization is only influenced by the method parameter jsonview. The serialization is now always only influenced by the method (or class level) jsonview.
For (1), the user parameter does not use any JsonView anymore.
For (2), this means that the user parameter correctly uses Views.Public for deserialization, and for serialization Views.Private gets used

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit a23972d.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.

[geoand]

Thanks!