`no-legacy-imports` autofixer sometimes uses the wrong package replacements

[Windvis]

I just ran the no-legacy-imports autofixer in our 6.12 classic project and noticed that it doesn't use the correct replacement for some packages.

In our app, both the JSONAPISerializer and Adapter were replaced with the wrong import.

- import JSONAPIAdapter from '@ember-data/adapter/json-api';
+ import JSONAPIAdapter from '@warp-drive/legacy/model';

While it should have been the following instead:

- import JSONAPIAdapter from '@ember-data/adapter/json-api';
+ import { JSONAPIAdapter } from '@warp-drive/legacy/adapter/json-api';

It looks like the mapping file is simply incorrect for these entries (and potentially others):

warp-drive/packages/eslint-plugin-warp-drive/src/public-exports-mapping-5.5.enriched.json

Lines 278 to 289 in e3a30bb

	{
	"filePath": "packages/adapter/src/json-api.ts",
	"module": "@ember-data/adapter/json-api",
	"export": "default",
	"typeOnly": false,
	"replacement": {
	"module": "@warp-drive/legacy/model",
	"export": "default",
	"sourceFile": "warp-drive-packages/legacy/src/model.ts",
	"typeOnly": false
	}
	},

[runspired]

@Baltazore were you still working on some updates here?

[Baltazore]

@runspired sorry for the wait. Unfortunately I haven't been working on project for quite some time and I don't think I will be back before end of may. So don't wait for me here