[BUG] Error when importing content-types with component field and localization

[landoephan]

Describe the bug
The import doesn't work when I have a content type with a component field and localization enabled.

The error message is error: link must be a object type, but the final value was: '8'

When I disable the localization for that content type the import works. The exported json looks like this:

{
	"version": 2,
	"data": {
		"helpers.portal-link": {
			"8": {
				"id": 8,
				"url": "test",
				"text": "test"
			},
			"10": {
				"id": 10,
				"url": "test",
				"text": "test 2"
			}
		},
		"api::test-with-comp.test-with-comp": {
			"2": {
				"id": 2,
				"createdAt": "2022-12-08T12:51:32.164Z",
				"updatedAt": "2022-12-08T12:53:37.559Z",
				"publishedAt": "2022-12-08T12:51:33.229Z",
				"link": 8,
				"createdBy": null,
				"updatedBy": null
			},
			"3": {
				"id": 3,
				"createdAt": "2022-12-08T12:57:02.387Z",
				"updatedAt": "2022-12-08T12:57:02.387Z",
				"publishedAt": null,
				"link": 10,
				"createdBy": null,
				"updatedBy": null
			}
		}
	}
}

And with the localization activated:

{
	"version": 2,
	"data": {
		"api::test-with-comp.test-with-comp": {
			"4": {
				"id": 4,
				"createdAt": "2022-12-08T13:00:22.485Z",
				"updatedAt": "2022-12-08T13:01:31.555Z",
				"publishedAt": "2022-12-08T13:00:24.717Z",
				"locale": "de",
				"link": 11,
				"localizations": [],
				"createdBy": null,
				"updatedBy": null
			},
			"5": {
				"id": 5,
				"createdAt": "2022-12-08T13:00:33.565Z",
				"updatedAt": "2022-12-08T13:01:31.564Z",
				"publishedAt": "2022-12-08T13:00:34.888Z",
				"locale": "de",
				"link": 12,
				"localizations": [],
				"createdBy": null,
				"updatedBy": null
			}
		},
		"helpers.portal-link": {
			"11": {
				"id": 11,
				"url": "test",
				"text": "test"
			},
			"12": {
				"id": 12,
				"url": "test",
				"text": "test 2"
			}
		}
	}
}

When I remove the component from my content type everything works aswell, no matter if localization is enabled or not.

To Reproduce
Steps to reproduce the behavior:

1. Create a content-type with localization enabled and a field with a component
2. create some content for that content-type
3. export that content using this plugin
4. import the exported content again
5. see error

Expected behavior
Data is imported without errors

[Baboo7]

@landoephan this issue is fixed in version 1.19.0. Thank you for the detailed report!