Importers: create standard API response entities
<!--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=452232)
</details>
<!--IssueSummary end-->
We will implement a set of standard API responses for import endpoints. To avoid breaking changes, we only require new endpoints to return this data. We may update existing endpoints to include these response bodies, but only additively.
A new response:
```ruby
{
"foo": "bar"
}
```
An old response, retro-fitted:
```ruby
{
"old_foo": "old_bar",
"v2_response": {
"foo": "bar
}
}
```
- [Martin's comment](https://gitlab.com/gitlab-org/gitlab/-/issues/439455#note_1753492925)
- [Luke's comment](https://gitlab.com/gitlab-org/gitlab/-/issues/438496#note_1790230881)
- [Me asking Justin about non-public API usage](https://gitlab.com/gitlab-org/gitlab/-/issues/439455#note_1800475789)
issue