feat: handle large object storage by clearing spec and updating annotations

[matthyx]

Summary by CodeRabbit

• Bug Fixes
  • Improved handling of oversized objects during storage operations. Objects exceeding size limits now persist with metadata indicating the constraint instead of failing completely. Content is automatically optimized during creation and update operations to address size restrictions while maintaining essential metadata.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Modified error handling in file storage operations. When PreSave encounters ObjectTooLargeError, the code now clears the object's Spec, annotates it with TooLarge status, and continues saving instead of returning the error. A new helper function clearSpec resets object Spec fields to their zero value.

Changes

Cohort / File(s)	Summary
Storage Error Handling pkg/registry/file/storage.go	Modified CreateWithConn, GuaranteedUpdateWithConn, and GuaranteedUpdate to handle ObjectTooLargeError by clearing Spec and setting TooLarge annotation instead of returning error. Added clearSpec() helper function to reset Spec fields. Ensured annotations are initialized to prevent nil map dereferences.

Estimated Code Review Effort

🎯 3 (Moderate) | ⏱️ ~22 minutes

Poem

🐰 A rabbit hops through storage paths so deep,
When objects grow too large to keep,
We trim the specs with careful care,
Mark them "TooLarge" in annotations fair! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: handling large object storage by clearing the spec and updating annotations, which directly matches the core functionality changes in the pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Summary:

• License scan: failure
• Credentials scan: failure
• Vulnerabilities scan: success
• Unit test: success
• Go linting: success