no-legacy-imports should account for more recent exports

[runspired]

We added (and thus exposed via *) some exports, mostly types. We should either (A) also account for new exports added over time in our book-keeping or (B) say the older packages have their exports frozen entirely and to gain access to new things you must shift. I suspect (A) is better, and what we should do is create a mapping of file-to-file for any unknown tokens so we aren't constantly updating the list.

We also don't error for legacy import paths if they import tokens not in the current list - we should.

[Baltazore]

to account for new imports - just need to gather them and re-create the map using scripts.

I think I forgot step that we discussed a month or so ago - we need somehow make exports in 5.5 and onward the same exports that we had before.

I can prepare PR with this changes first, and re-run scripts to have updated map in lint.

I also will re-check the types exports