feat(git): add size limits for git operations

- Added MAX_CHERRY_PICK_PATCH_BYTES limit of 100MB for cherry-pick operations
- Added MAX_ACTION_CONTENT_BYTES limit of 100MB for commit action content
- Added MAX_COMMIT_MESSAGE_BYTES limit of 10MB for commit messages
- Added MAX_CHECK_REVISIONS limit of 10,000 for revision checks
- Added MAX_REBASE_COMMITS limit of 10,000 for rebase operations
- Added MAX_REBASE_PATCH_BYTES limit of 100MB for rebase patches
- Added MAX_RESOLUTION_CONTENT_BYTES limit of 100MB for merge conflict resolutions
- Added MAX_REVERT_PATCH_BYTES limit of 100MB for revert operations
- Return InvalidArgument error when size limits are exceeded with descriptive messages

remote/mirror.rs

@@ -16,6 +16,13 @@ impl GitBare {
             &request.remote_name
         };
         crate::sanitize::validate_ref_name(remote_name)?;
+
+        const MAX_REFSPECS: usize = 100;
+        if request.refspecs.len() > MAX_REFSPECS {
+            return Err(crate::error::GitError::InvalidArgument(format!(
+                "too many refspecs (max {MAX_REFSPECS})"
+            )));
+        }
         for rs in &request.refspecs {
             crate::sanitize::validate_refspec(rs)?;
         }
@@ -134,6 +141,13 @@ impl GitBare {
             &request.remote_name
         };
         crate::sanitize::validate_ref_name(remote_name)?;
+
+        const MAX_FETCH_REFSPECS: usize = 100;
+        if request.refspecs.len() > MAX_FETCH_REFSPECS {
+            return Err(crate::error::GitError::InvalidArgument(format!(
+                "too many refspecs (max {MAX_FETCH_REFSPECS})"
+            )));
+        }
         for rs in &request.refspecs {
             crate::sanitize::validate_refspec(rs)?;
         }