Add 302 error handling to group imports
<!--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>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=432325)
</details>
<!--IssueSummary end-->
<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
### Proposal
Add 302 error handling (and possibly more HTTP status handling) to group imports.
During a customer emergency ([link (ZD internal)](https://gitlab.zendesk.com/agent/tickets/472449)) the logs provided a 302 redirect but the customer was receiving a generic banner for [Importing the group failed](https://gitlab.com/gitlab-org/gitlab/-/blob/a4283e9cad3466ba54d181e6ae81f8113081b184/app/assets/javascripts/import_entities/import_groups/constants.js#L12).
302 redirects are usually SSO sign in requests (but not always).
This feature request may also be a duplicate of gitlab-org/gitlab#372714+
<!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. -->
<!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section.
-->
<!-- Label reminders
Use the following resources to find the appropriate labels:
- Use only one tier label choosing the lowest tier this is intended for
- https://gitlab.com/gitlab-org/gitlab/-/labels
- https://about.gitlab.com/handbook/product/categories/features/
-->
issue