fix(openapi): integer types should be i64

[katiemckeon]

🔄 Pull Request

📝 Description

Relates to this issue. The codegen that produces our internal client was converting OpenAPI integer types to i32. This caused certain fields within the circuit info response to overflow and deserialization of those responses failed in an opaque way.

🔗 Related Tickets & Documents

• Related Issue #
• Closes #

📋 Type of PR (check all applicable)

• 🔨 Refactor
• ✨ Feature
• 🐛 Bug Fix
• ⚡ Optimization
• 📚 Documentation Update

💭 Developer Notes

The main content in this PR is within the api update script:

# Patch OpenAPI generator problematic integer->i32 conversion
sed -i 's/i32/i64/g' openapi/src/models/*.rs

This is a broader surface area than just circuit details and will apply to any future API update. There are minor performance implications, but I cannot think of any current use cases where the involved API fields overwhelm memory. It is much more likely that a different user will encounter issues with e.g. pagination

🧪 Testing Instructions

Groth16 Sp1 program circuit detail deserialized successfully

✅ Testing Status

• Yes, tests added/updated. (Unit tests touching the circuit info response now include an i64 value)
• No tests needed because: please explain why
• Help needed with testing