fix: minor tw4 fixes and lint tw format

frontend/src/pages/organization/AccessManagementPage/AccessManagementPage.tsx

@@ -76,7 +76,7 @@ export const AccessManagementPage = () => {
   const hasNoAccess = tabSections.every((tab) => tab.isHidden);
 
   return (
-    <div className="container mx-auto flex flex-col justify-between bg-bunker-800 text-white">
+    <div className="bg-bunker-800 container mx-auto flex flex-col justify-between text-white">
       <Helmet>
         <title>{t("common.head-title", { title: t("settings.org.title") })}</title>
       </Helmet>
@@ -86,12 +86,12 @@ export const AccessManagementPage = () => {
           description="Manage fine-grained access for users, groups, roles, and identities within your organization resources."
         />
         {!currentOrg.shouldUseNewPrivilegeSystem && (
-          <div className="mt-4 mb-4 flex flex-col rounded-r border-l-2 border-l-primary bg-mineshaft-300/5 px-4 py-2.5">
+          <div className="border-l-primary bg-mineshaft-300/5 mb-4 mt-4 flex flex-col rounded-r border-l-2 px-4 py-2.5">
             <div className="mb-1 flex items-center text-sm">
-              <FontAwesomeIcon icon={faInfoCircle} size="sm" className="mr-1.5 text-primary" />
+              <FontAwesomeIcon icon={faInfoCircle} size="sm" className="text-primary mr-1.5" />
               Your organization is using legacy privilege management
             </div>
-            <p className="mt-1 mb-2 text-sm text-bunker-300">
+            <p className="text-bunker-300 mb-2 mt-1 text-sm">
               We&apos;ve developed an improved privilege management system to better serve your
               security needs. Upgrade to our new permission-based approach that allows you to
               explicitly designate who can modify specific access levels, rather than relying on