Dysfunctional PatchRequest Deserialization in Quarkus Example

It looks like the deserialization of `PatchRequest` payloads in the quarkus sample doesn't work properly. Here's the request we're sending:

`PATCH http://:/v2/Users/`
```json
{
"schemas": [
"urn:ietf:params:scim:api:messages:2.0:PatchOp"
],
"Operations": [
{
"op": "replace",
"path": "userName",
"value": "newName"
}
]
}
```

However, debugging the patch endpoint reveals that the list of patch operations isn't populated:


This does, however, work well with the Spring Boot sample, so it looks like this is something specific to the Quarkus sample app. Any help with that would be greatly appreciated - no idea what's causing this.