feat: enhance security by implementing HttpOnly refresh tokens and in-memory access token management

- Added isomorphic-dompurify for improved XSS protection
- Refactored token storage to use in-memory management for access tokens
- Implemented server-side route handlers for OAuth token management
- Introduced security headers in next.config.js
- Removed client-side exposure of client_secret and sensitive tokens
- Updated API interceptors to handle token refresh logic
- Cleaned up cookie management for refresh tokens

services/response.js

@@ -11,30 +11,6 @@ export const request = {
       },
       removeTokenHead
     ),
-  getToken: (grant_type, client_id, client_secret, uuid, code, scope = "nobat724") => {
-    const formData = new URLSearchParams();
-    formData.append("grant_type", grant_type);
-    formData.append("client_id", client_id);
-    formData.append("client_secret", client_secret);
-    formData.append("uuid", uuid);
-    formData.append("code", code);
-    formData.append("scope", scope);
-
-    return api.post("oauth/token", formData, {
-      headers: {
-        "Content-Type": "application/x-www-form-urlencoded",
-        Authorization: "",
-      },
-    });
-  },
-  postRefreshToken: (formData) => {
-    return api.post("oauth/token", formData, {
-      headers: {
-        "Content-Type": "application/x-www-form-urlencoded",
-        Authorization: "",
-      },
-    });
-  },
   getUserProfile: (uuid) => api.get(`/api/v1/user-profile/${uuid}`, { requireAuth: true }),
   postUserProfile: (data) => api.post("api/v1/user-profile", data, { requireAuth: true }),
   patchUserProfile: (data, uuid) =>