Move StrictInt ahead of StrictFloat in model

In newer pydantic this converts a 0 to 0.0 when serializing
to Json and this breaks when reading a record back that is
meant to be an integer. This changes in pydantic 2.2 whereas
2.1 behaved like 1.0.

This happens because the dynamic subclasses apply dynamic constraints
based on the specific record data model so they know that something
must be an integer.

python/lsst/daf/butler/core/dimensions/_records.py

@@ -146,7 +146,7 @@ class SerializedDimensionRecord(_BaseModelCompat):
     )
 
     # Use strict types to prevent casting
-    record: dict[str, None | StrictFloat | StrictStr | StrictBool | StrictInt | tuple[int, int]] = Field(
+    record: dict[str, None | StrictInt | StrictFloat | StrictStr | StrictBool | tuple[int, int]] = Field(
         ...,
         title="Dimension record keys and values.",
         examples=[