Don't rely on setter present when passing default values for newly created items

[StefanPenndorf]

Currently EntityQuery tries to provide default values for all columns/properties defined in the QueryDefinition when calling constructItem. This fails if there is no setter (e.g. it's a calculated or read-only property).

Solution: Don't try to call a setter/provide a default if none exists. Maybe you'd like to print a warning but since there is no way to disable the warning it might be confusing. One way might be to enable optional default values.