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/get_protection_rule.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;
@@ -22,7 +22,7 @@ pub struct PathParams {
 ///
 /// Returns detailed information about a specific branch protection rule.
 /// Requires read access to the repository.
-/// 
+///
 /// Returns the complete protection rule with all configuration details including:
 /// - Branch name pattern
 /// - Required approvals and status checks
@@ -52,7 +52,12 @@ pub async fn get_protection_rule(
 ) -> Result<HttpResponse, AppError> {
     let rule = service
         .repo
-        .repo_get_protection_rule(&session, &path.workspace_name, &path.repo_name, path.rule_id)
+        .repo_get_protection_rule(
+            &session,
+            &path.workspace_name,
+            &path.repo_name,
+            path.rule_id,
+        )
         .await?;
 
     Ok(HttpResponse::Ok().json(ApiResponse::new(rule)))