feat: improve PAM account update handling with enhanced error management

- Added try-catch block to handle potential database errors during account updates.
- Implemented specific error handling for unique constraint violations, providing clearer feedback for duplicate account names.
- Updated AWS IAM account schema to indicate that credential rotation is not supported, defaulting to false.

backend/src/ee/services/pam-account/pam-account-service.ts

@@ -290,6 +290,7 @@ export const pamAccountServiceFactory = ({
       return decryptAccount(account, account.projectId, kmsService);
     }
 
+    try {
       const updatedAccount = await pamAccountDAL.updateById(accountId, updateDoc);
 
     return {
@@ -301,6 +302,15 @@ export const pamAccountServiceFactory = ({
         rotationCredentialsConfigured: !!resource.encryptedRotationAccountCredentials
       }
     };
+    } catch (err) {
+      if (err instanceof DatabaseError && (err.error as { code: string })?.code === DatabaseErrorCode.UniqueViolation) {
+        throw new BadRequestError({
+          message: `Account with name '${name}' already exists for this path`
+        });
+      }
+
+      throw err;
+    }
   };
 
   const deleteById = async (id: string, actor: OrgServiceActor) => {

backend/src/ee/services/pam-resource/aws-iam/aws-iam-resource-schemas.ts

@@ -67,7 +67,9 @@ export const AwsIamAccountSchema = BasePamAccountSchema.extend({
 });
 
 export const CreateAwsIamAccountSchema = BaseCreatePamAccountSchema.extend({
-  credentials: AwsIamAccountCredentialsSchema
+  credentials: AwsIamAccountCredentialsSchema,
+  // AWS IAM accounts don't support credential rotation - they use role assumption
+  rotationEnabled: z.boolean().default(false)
 });
 
 export const UpdateAwsIamAccountSchema = BaseUpdatePamAccountSchema.extend({