Implement Omada device management and enhance payment processing

- Added new omada-actions.ts file to handle fetching and updating device groups in Omada.
- Updated authMiddleware to include new payment routes.
- Enhanced createPayment function to add devices to a group upon successful payment verification.
- Improved payment verification process to include device management.
- Refactored PaymentsTable and DevicesToPay components for better UI and state handling.
- Removed unused hasSession function from auth-guard.ts for cleaner code.

components/devices-to-pay.tsx

@@ -42,7 +42,7 @@ export default function DevicesToPay({
   return (
     <div className="w-full">
       <div className="p-2 flex flex-col gap-2">
-        <h3 className="title-bg my-1 font-semibold text-lg">
+        <h3 className="title-bg my-1 p-2 font-semibold text-lg">
           {!payment?.paid ? "Devices to pay" : "Devices Paid"}
         </h3>
         <div className="flex flex-col gap-2">
@@ -71,7 +71,7 @@ export default function DevicesToPay({
                 accountNo="90101400028321000"
               />
               {payment?.paid ? (
-                <Button size={"lg"} variant={"secondary"} disabled className="text-green-400 bg-green-800">Payment Verified</Button>
+                <Button size={"lg"} variant={"secondary"} disabled className="dark:text-green-200 text-green-900 bg-green-500/20 uppercase font-semibold">Payment Verified</Button>
               ) : (
                 <Button
                   disabled={verifying}