refactor(api): reorder imports and update code formatting across repository endpoints

- Reordered actix-web imports to standardize import order
- Reordered crate module imports to follow alphabetical ordering
- Updated function calls to use multi-line formatting for better readability
- Standardized blank lines around documentation comments
- Applied consistent formatting to response handling methods
- Normalized import organization across all repository-related API files
- Improved code consistency and maintainability through standardized formatting
- Applied formatting updates to all repository endpoint implementations

api/repo/match_protection.rs

@@ -1,8 +1,8 @@
-use actix_web::{web, HttpResponse};
+use actix_web::{HttpResponse, web};
 use serde::Deserialize;
 use utoipa::IntoParams;
 
-use crate::api::response::{ApiResponse, ApiErrorResponse};
+use crate::api::response::{ApiErrorResponse, ApiResponse};
 use crate::error::AppError;
 use crate::models::repos::BranchProtectionRule;
 use crate::service::AppService;
@@ -26,7 +26,7 @@ pub struct QueryParams {
 ///
 /// Checks if a branch name matches any protection rule in the repository.
 /// Requires read access to the repository.
-/// 
+///
 /// Returns the matching protection rule if found, or null if no rules match.
 /// Useful for determining what protections apply to a specific branch before performing operations.
 #[utoipa::path(