Added type checking for object-type values in field and argument pres…

…ets (#1566)

<!-- The PR description should answer 2 important questions: -->

### What
Enabled type checking for preset values provided to fields or arguments
of object types in type, command, or model permissions. This check is
controlled by a compatibility flag, with the date set to the next
release. A warning will be issued for projects with older compatibility
dates. Type check also extended to fields within an object having object
types (nested fields).

### How

<!-- How is it trying to accomplish it (what are the implementation
steps)? -->
Type-checking functions now report issues for object-type value
type-check failures. These are raised as warnings for existing projects
and as strict errors for new projects or those with the latest
compatibility dates.

V3_GIT_ORIGIN_REV_ID: 840c4f2e5ef2bd9c5c307528c3f797fe7ba2070b

v3/changelog.md

@@ -4,6 +4,10 @@
 
 ### Added
 
+- Added type checking for object-type values in field presets within type
+  permissions and for argument presets in model or command permissions.
+- Allow environment variables to be used in permission filters.
+
 ### Fixed
 
 ### Changed
@@ -15,7 +19,6 @@
 - Added configuration for headers in response to client for requests handled by
   the pre-route plugin hook.
 - Added OpenAPI schema for filter parameters in JSONAPI
-- Allow environment variables to be used in permission filters.
 
 ### Fixed
 

v3/crates/compatibility/src/compatibility_date.rs

@@ -155,5 +155,9 @@ pub fn get_compatibility_date_for_flag(flag: Flag) -> Option<CompatibilityDate>
         Flag::DisallowDuplicateAggregateFunctionDefinitionsForScalarType => {
             Some(new_compatibility_date(2025, 1, 25))
         }
+        Flag::TypecheckObjectTypeValuesInPresets => {
+            // TODO Set a compatibility date during the next release.
+            None
+        }
     }
 }