fix: correct middleware layer ordering in QR routes

Same issue as hackathon routes - qr_auth_middleware needs Arc<PgPool>
from Extension but was outermost layer. Swapped order so pool is
available when middleware runs.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

imphnen-cms/src/qr/campaigns/infrastructure/http/routes.rs

@@ -36,6 +36,6 @@ pub fn qr_campaigns_routes(pool: Arc<PgPool>) -> Router {
 		.route("/campaigns/{id}", delete(delete_campaign_handler))
 		.route("/campaigns/process-image", post(process_image_handler))
 		.layer(Extension(service))
-		.layer(Extension(pool))
 		.layer(from_fn(qr_auth_middleware))
+		.layer(Extension(pool))
 }

imphnen-cms/src/qr/users/infrastructure/http/routes.rs

@@ -32,6 +32,6 @@ pub fn qr_users_routes(pool: Arc<PgPool>) -> Router {
 		.route("/users/{id}/role", put(update_role_handler))
 		.route("/users/{id}", delete(delete_user_handler))
 		.layer(Extension(service))
-		.layer(Extension(pool))
 		.layer(from_fn(qr_auth_middleware))
+		.layer(Extension(pool))
 }