feat: Allow syntetic object fields in resources mapped to a model

[devdevx]

Feature Request

When I define a resource mapped to a model, I want to also support syntetic object fields.

For example:

project_resource:

{
  "id": 1
  "name": "Test",
  "permissions": {
     "edit": false
  }
}

project_model

{
  "id": 1
  "name": "Test"
}

The expected result should be a generated code where all the resource fields that exists in the model are populated and the rest of fields are only generated.

The current result is an error thrown by the getClass method