WorkspacesToBeReturnedUpdater update query performance
<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Work on this issue](https://contributors.gitlab.com/manage-issue?action=work&projectId=278964&issueIid=425518) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=425518) </details> <!--IssueSummary end--> MR Pending # Description Check the expected max rows and improve [WorkspacesToBeReturnedUpdater query update performance](https://gitlab.com/gitlab-org/gitlab/-/blob/6343b14aad94cebaadf41b5437531d6c863bf57a/ee/lib/remote_development/workspaces/reconcile/persistence/workspaces_to_be_returned_updater.rb) Follow-up from "Force full reconciliation logic for workspaces" # Acceptance criteria - [ ] Identify max number of records - [ ] Solution: Do a batched update and consider doing a full update rather than partial
issue