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/remove_member.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::service::AppService;
 use crate::session::Session;
@@ -21,15 +21,15 @@ pub struct PathParams {
 ///
 /// Revokes a user's access to the repository.
 /// Requires Admin role or higher in the repository.
-/// 
+///
 /// Restrictions:
 /// - Cannot remove the repository owner (use transfer_owner instead)
 /// - Cannot remove members with equal or higher role than your own
-/// 
+///
 /// Effects:
 /// - Member loses all access to the repository
 /// - Member is removed from all repository activities
-/// 
+///
 /// Returns success message on completion.
 #[utoipa::path(
     delete,
@@ -56,7 +56,12 @@ pub async fn remove_member(
 ) -> Result<HttpResponse, AppError> {
     service
         .repo
-        .repo_remove_member(&session, &path.workspace_name, &path.repo_name, path.member_id)
+        .repo_remove_member(
+            &session,
+            &path.workspace_name,
+            &path.repo_name,
+            path.member_id,
+        )
         .await?;
 
     Ok(HttpResponse::Ok().json(ApiResponse::new("Member removed successfully".to_string())))