Fix bulk_assign tests to not depend on removed member mutation

test_bulk_assign_data_rows and test_bulk_assign_data_rows_with_allowed_statuses
relied on the project_based_user fixture, which creates an org member via the
addMembersToOrganization mutation. That mutation was removed from the API back
in intelligence #11829 (a2bdf13f69, 2022-11-15), so the fixture has been
erroring at setup ever since (masked by the chronically-red integration suite).

There is no public-API replacement that yields an assignable member without
email-invite acceptance (invite_user returns a pending Invite, not a User).
bulk_assign_data_rows only needs a valid member uid, so assign to the current
authenticated user (client.get_user()) instead. This keeps the live
bulk_assign_data_rows feature under test rather than dropping coverage.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: mrobers1982

libs/labelbox/tests/integration/test_bulk_assign.py

@@ -1,11 +1,9 @@
 from labelbox.schema.task_assignment_status import TaskAssignmentStatus
 
 
-def test_bulk_assign_data_rows(
-    configured_batch_project_with_label, project_based_user
-):
+def test_bulk_assign_data_rows(configured_batch_project_with_label, client):
     project, _, data_row, _ = configured_batch_project_with_label
-    user = project_based_user
+    user = client.get_user()
 
     result = project.bulk_assign_data_rows(
         user_id=user.uid,
@@ -15,10 +13,10 @@ def test_bulk_assign_data_rows(
 
 
 def test_bulk_assign_data_rows_with_allowed_statuses(
-    configured_batch_project_with_label, project_based_user
+    configured_batch_project_with_label, client
 ):
     project, _, data_row, _ = configured_batch_project_with_label
-    user = project_based_user
+    user = client.get_user()
 
     result = project.bulk_assign_data_rows(
         user_id=user.uid,