Add missing MarshalJSON/UnmarshalJSON for integer:string models

[c1-dev-bot]

Summary

• Adds custom MarshalJSON/UnmarshalJSON methods to 17 model files that have integer:"string" struct tags but were missing the custom serialization methods
• Follows the same fix pattern applied in PR temp fix for unmarsheling issue #97 for the Escalation model
• Without these methods, Go's standard json.Marshal/json.Unmarshal does not process the integer:"string" tag, so int64 fields serialized as quoted strings by the API (e.g. "123") fail to unmarshal correctly

Affected Models

File	Fields with integer:"string"
AppResourceInput	grantCount
AutomationExecutionRef	id
ExecuteAutomationResponse	executionId
FacetRange	count, from, to
Facets	count
FacetValue	count
FileField	maxFileSize
Int64Field	defaultValue
Int64Rules	const, gt, gte, lt, lte, in, notIn
NumberField	maxValue, minValue, step
PayloadWorkflowStep	workflowExecutionId
RequestCatalogView	memberCount
SearchAutomationExecutionsRequest	executionId
SFixed64Rules	const, gt, gte, lt, lte, in, notIn
SInt64Rules	const, gt, gte, lt, lte, in, notIn
TaskAuditErrorResult	errorCount
WebhookSourceWorkflowStep	workflowExecutionId

Root Cause

The ConductorOne API serializes int64 fields as JSON strings (e.g. "grantCount": "42" instead of "grantCount": 42). The SDK uses a custom integer:"string" struct tag to indicate this, and the pkg/utils package provides MarshalJSON/UnmarshalJSON functions that handle this tag. However, these utility functions are only invoked when a struct has custom MarshalJSON/UnmarshalJSON methods that delegate to them. Without these methods, Go's standard JSON encoder/decoder ignores the custom tag entirely, causing unmarshaling errors when it encounters a string where it expects a number.

Test plan

• go build ./... passes
• go test ./... passes
• Manual testing with SDK operations that return/accept AppResourceInput, FacetRange, and other affected models

---

Automated PR Notice

This PR was automatically created by c1-dev-bot as a potential implementation.

This code requires:

• Human review of the implementation approach
• Manual testing to verify correctness
• Approval from the appropriate team before merging