Add support for Jackson annotations

[ZdravDimOracle]

This pull request adds support for flex columns and unnest keyword via Jackson annotations.

For flex columns we use @JsonAnyGetter and @JsonAnySetter annotations.
If we want to specify a property as a flex column, we use any of these annotations two on a property, also at most one property can have any combination of these two annotations, since there can only be one flex column.

Example:

@JsonView(entity = Person.class)
public class PersonView {
	@Id
	@GeneratedValue(GeneratedValue.Type.IDENTITY)
	private Long id;
	private String firstname;
	private String lastname;

	@JsonAnyGetter
	@JsonAnySetter
	private Map<String, Object> extras;
}

This creates a view like so:

CREATE OR REPLACE JSON RELATIONAL DUALITY VIEW person_view 
AS SELECT JSON {
    '_id': p.id,
	'firstname': p.firstname,
    'lastname': p.lastname,
    p.extras AS FLEX COLUMN
}
FROM TBL_PERSON p
WITH UPDATE INSERT DELETE;

For the unnest feature, we use @JsonUnwrapped annotation to specify which property will be unnested.

Example:

@JsonSubView(entity = Apartment.class, alias = "asw")
public record ApartmentSubView(
    @EmbeddedId
    @JsonUnwrapped
    ApartmentId apartmentId
) {}

@JsonView(entity = Building.class, alias = "bw")
public class BuildingView {
    @Id
    @GeneratedValue(GeneratedValue.Type.IDENTITY)
    private Long id;

    @Relation(Relation.Kind.ONE_TO_MANY)
    private List<ApartmentSubView> apartments;
}

This will create a JSON Duality View like so:

CREATE OR REPLACE JSON RELATIONAL DUALITY VIEW building_view
AS SELECT JSON {
	'_id': b.id,
	UNNEST (
		SELECT JSON {
			'apartments': [
				SELECT JSON {
					'buildingId': ap.building_id,
					'flatId': ap.flat_id
				}
				FROM TBL_APARTMENT ap
				WITH UPDATE INSERT DELETE
				WHERE building_apartment."APARTMENT_APARTMENT_ID_BUILDING_ID"=ap."BUILDING_ID"
				AND building_apartment."APARTMENT_APARTMENT_ID_FLAT_ID"=ap."FLAT_ID"
			]
		}
		FROM building_apartment ba
		WITH UPDATE INSERT DELETE
		WHERE b."ID"=building_apartment."BUILDING_ID"
		)
	}
	FROM TBL_BUILDING b
	WITH UPDATE INSERT DELETE;

[graemerocher]

we need to clearly document which Jackson annotations are supported and how they map to duality views in the duality views section of the docs

[dstepanov]

Any specific Jackson support should be part of Serde

[graemerocher]

@dstepanov serde doesn't make sense this context, it is about the mapping from java class to duality view. Which does use serde under the covers for runtime marshalling but this PR makes it also take into account for schema generation of the views