Migration path towards /zoneless

[timdeschryver]

Should the /zoneless subpackage become the default.
If so, how should we do it without creating too much hassle to existing codebases?

Proposal:

• re-export the current library as a /zone(?) sub package => feature release
• provide a schematic to update existing import paths to /zone and flag the zone sub package as deprecated => feature release
• make /zoneless the default (with a migration schematic) and remove the /zoneless sub package => major change

[ThiloAschebrock]

I support this proposal and note that changes to sub-packages should ideally be synced with the eslint plugin, see testing-library/eslint-plugin-testing-library#1366.