fix: use dynamic key counts in integration test

CreateHeadscaleEnv creates additional pre-auth keys per user, so use
actual counts rather than hardcoded values for assertions.

Author: newbdez33

integration/auth_key_test.go

@@ -792,21 +792,33 @@ func TestDeleteUserPreservesOtherUsersPreAuthKeys(t *testing.T) {
 	_, err = headscale.CreateAuthKey(user2.GetId(), true, false)
 	require.NoError(t, err)
 
-	// Verify 3 keys exist
+	// Count keys per user before deletion
 	keysBefore, err := headscale.ListPreAuthKeys()
 	require.NoError(t, err)
-	assert.Len(t, keysBefore, 3, "should have 3 keys before deletion")
+
+	var user1KeysBefore, user2KeysBefore int
+	for _, k := range keysBefore {
+		switch k.GetUser().GetName() {
+		case "user1":
+			user1KeysBefore++
+		case "user2":
+			user2KeysBefore++
+		}
+	}
+	t.Logf("Before deletion: user1 has %d keys, user2 has %d keys", user1KeysBefore, user2KeysBefore)
+	require.Greater(t, user1KeysBefore, 0, "user1 should have keys")
+	require.Greater(t, user2KeysBefore, 0, "user2 should have keys")
 
 	// Delete user2
 	err = headscale.DeleteUser(user2.GetId())
 	require.NoError(t, err)
 
-	// Verify only user1's 2 keys remain
+	// Verify only user1's keys remain — user2's keys should be gone
 	keysAfter, err := headscale.ListPreAuthKeys()
 	require.NoError(t, err)
-	assert.Len(t, keysAfter, 2,
-		"expected 2 keys for user1 after deleting user2, but got %d — DestroyUser should only delete the target user's keys (issue #3154)",
-		len(keysAfter))
+	assert.Len(t, keysAfter, user1KeysBefore,
+		"expected %d keys for user1 after deleting user2, but got %d — DestroyUser should only delete the target user's keys (issue #3154)",
+		user1KeysBefore, len(keysAfter))
 
 	for _, key := range keysAfter {
 		assert.Equal(t, user1.GetName(), key.GetUser().GetName(),