chore(openapi): format tags in API documentation for consistency

Updated the OpenAPI specification to format the 'tags' property as an array on multiple endpoints, ensuring consistent styling across the documentation. Additionally, simplified JSX return statements in the BookingsPage and AdminEventBookingsTab components for improved readability.

app/(dashboard)/bookings/page.tsx

@@ -136,11 +136,7 @@ const BookingsPage = () => {
 
               if (!isCancelledLike || !reason) return '—'
 
-              return (
-                <span className="max-w-[220px] whitespace-pre-wrap break-words text-xs text-secondary-20">
-                  {reason}
-                </span>
-              )
+              return <span className="max-w-[220px] whitespace-pre-wrap break-words text-xs text-secondary-20">{reason}</span>
             },
             checkedInAt: (_row, cellValue) => formatPersianDate(cellValue),
             createdAt: (_row, cellValue) => formatPersianDate(cellValue),

features/events/detail/admin-event-detail/AdminEventBookingsTab.tsx

@@ -120,11 +120,7 @@ const AdminEventBookingsTab = ({ eventId, eventStatus, onCheckedIn }: AdminEvent
 
             if (!isCancelledLike || !reason) return '—'
 
-            return (
-              <span className="max-w-[220px] whitespace-pre-wrap break-words text-xs text-secondary-20">
-                {reason}
-              </span>
-            )
+            return <span className="max-w-[220px] whitespace-pre-wrap break-words text-xs text-secondary-20">{reason}</span>
           },
           checkedInAt: (_row, cellValue) => formatPersianDate(cellValue),
           createdAt: (_row, cellValue) => formatPersianDate(cellValue),