Enable filtering direct transfer results by statuses available now in FE
<!--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=463317) - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=463317) </details> <!--IssueSummary end--> ### Problem As described in https://gitlab.com/gitlab-org/gitlab/-/issues/441405+ direct transfer history page lacks the option to filter or order the results, for example by status badges. Searching for failed or partially completed imports of groups/projects takes time, because the user needs to click through the pages. Users are especially interested to see what if anything has failed. From user feedback: > “Other than clicking through the transfer history, is there an easier way to find transfer failures/errors?” Currently the [API provides parameters](https://gitlab.com/gitlab-org/gitlab/-/blob/657cad97d1cebd08cd22d9242159eb788247ffe9/lib/api/bulk_imports.rb#L130) to: * Sort by "Start date" (ascending or descending). * Filter by "Status": "created", "started", "finished", "timeout", "failed". Note that "Partially completed" is not a real status in the backend and is considered "finished". ### Proposed solution Create additional status on the BE, so that it's possible to filter by "Partially completed" and "Compete" statuses as well. From https://gitlab.com/gitlab-org/gitlab/-/issues/463317#note_1928088312: The best solution for this issue might be to add a new `status` to `BulkImport` for "partially completed" and update our code to set that status when the import has been partially completed and not fully completed. This would mean (going forward) that the `"finished"` status would mean completed, and the new status (let's say `"partially_finished"`) would mean partially completed. The API support would then [be automatic](https://gitlab.com/gitlab-org/gitlab/-/blob/657cad97d1cebd08cd22d9242159eb788247ffe9/lib/api/bulk_imports.rb#L132). We could [update here](https://gitlab.com/gitlab-org/gitlab/-/blob/9ade4ea34d4a403c800a7e601d4f6f8a95b6114c/app/services/bulk_imports/process_service.rb#L18) with something similar to the diff in https://gitlab.com/gitlab-org/gitlab/-/issues/463317#note_1928088312. And also [update `BulkImport#finished?`](https://gitlab.com/gitlab-org/gitlab/-/blob/f1db82fb4db620ce0cff4f3a9e2ff4277caaca48/app/models/bulk_import.rb#L100-102) to consider the new status to be a finished state also.
issue